[GRADLE-2783] JaCoCo plugin should provide a task to check that given code metrics are being met Created: 29/May/13 Updated: 08/Nov/16 Resolved: 08/Nov/16 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.6 |
Fix Version/s: | None |
Type: | New Feature | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 32 |
Description |
The Maven plugin has a check goal that checks that the code coverage metrics are being met. Can you do this with the JaCoCo Gradle plugin? |
Comments |
Comment by Gradle Forums [ 29/May/13 ] |
At the moment the JaCoCo plugin does not provide a check task. This plugin is incubating and pull requests are welcome cheers, |
Comment by Jeff D [ 10/Aug/15 ] |
Given that there's over 500 stars on github for the workaround to jacoco not being able to fail the build due to low levels of code coverage https://github.com/springfox/springfox/tree/fb780ee1f14627b239fba95730a69900b9b2313a/gradle This issue should receive attention. |
Comment by Aliaksandr Kazlou [ 24/Oct/15 ] |
Any progress on this one? Has it been scheduled for any of the upcoming Gradle release? |
Comment by Jim Sun [ 12/Jul/16 ] |
We really would like to see this jira moving forward. |
Comment by Barry O'Neill [ 27/Jul/16 ] |
Yeah - same here - it's gonna be hard to convince my team of gradle's value if it's going to end up with workaround like that from springfox. |
Comment by Eric Wendelin [ 08/Nov/16 ] |
Hello everyone. I have moved this to GitHub here: https://github.com/gradle/gradle/issues/824 — it is marked help-wanted for now, though this is one we will prioritize more highly if no one gets to it soon. Please upvote or continue the conversation there. |
Comment by Eric Wendelin [ 08/Nov/16 ] |
Moved to gradle/gradle#824 |