-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exclude the coverage files from the annotate step #5773
Exclude the coverage files from the annotate step #5773
Conversation
Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
This is something that was introduced with elastic#377 and was meant to be used with Jenkins to show coverage report. Now with Jenkins been replace and BK + Sonar enabled on the repo, there is no need to create such artifacts anymore. Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From 90min to 39sec on the annotate step, I'd say that fixes it. :) Thanks!
I had to look at the individual commit history to understand why this was the fix. You might want to update the PR description to keep the history easier to understand.
The problem was that the annotation plugin was reading the coverage files, which are converted to XML format with the help of the That was needed back when we combined Jenkins with some Jenkins plugins. We could keep creating that XML file, but we don't use it anymore, thus I removed it. |
Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
* Exclude the coverage files from the annotate step Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 8ebaa7d)
* Exclude the coverage files from the annotate step Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 8ebaa7d)
* Exclude the coverage files from the annotate step Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 8ebaa7d)
* Exclude the coverage files from the annotate step Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 8ebaa7d) Co-authored-by: Alexandros Sapranidis <alexandros@elastic.co> Co-authored-by: Julien Lind <julien.lind@elastic.co>
What does this PR do?
We noticed that the JUnit annotate step needed to take more time. This PR addresses that issue by not requiring it to parse the coverage files.
The generated coverage XML file was meant to be used in Jenkins to show the coverage report stats. The generated XML files were large, resulting in a problem with BK's JUnit annotate plugin.
Given that we don't operate any Jenkins instance, this PR removes the code that generated the XML coverage reports.
Now, coverage is reported only to Sonar.
Why is it important?
Reduce the time of CI step