pom - Adding jacoco as code coverage tool optionally #2665
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
Some external code analysis tools used in the community (deutsch telekom do have a SonarQube deployed in their infrastructure, we have a communautary Jenkins) can make use of the generated report by Jacoco to get insights on the code coverage of the solution. This commit proposes to activate the maven plugin as an optional profile which can (or not) be activated. Tested in the security-proxy as: ``` $ mvn clean test -PjacocoCoverage ``` This generates a target/site/jacoco path. Without: ``` $ mvn clean test ``` No code coverage report is generated, the behaviour is exactly the same as currently in master.
pmauduit
changed the title
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.
Some external code analysis tools used in the community (deutsch telekom
do have a SonarQube deployed in their infrastructure, we have a
community Jenkins) can make use of the generated report by Jacoco
to get insights on the code coverage of the solution.
This commit proposes to activate the maven plugin as an optional profile
which can (or not) be activated.
Tested in the security-proxy as:
This generates a target/site/jacoco path.
Without:
No code coverage report is generated, the behaviour is exactly the same
as currently in master.