Enable ci.jenkins.io coverage reporting #524
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable coverage reporting on ci.jenkins.io
Also fixes a javadoc generation warning but removing the exclusion of the jsr305 dependency from spotbugs annotations.
Testing done
Compare the job before this change (no coverage report) and the pull request build with its coverage report
Requested reviewers
I'd love to have a review from one or more of the people in the GSoC mentoring prep meeting, including @freyam, @krisstern , @gounthar , or @jmMeessen . Reviews not strictly required, but would be nice.