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.

It will be great if we could get the "check" feature added. The coverage information is pretty much useless if you cannot take an action based on it.

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

JaCoCo coverage validation is available with Gradle 3.4: https://github.com/gradle/gradle/issues/824.