Code coverage on short lived branches

(Dragan Marković) #1


In our project, we are using a plugin that calls the api and checks for quality gates on feature branches before merging to master. Right now, all short lived branches have a default quality gate that will fail if new issues > 0 && new bugs > 0. What i’m trying to introduce is a code coverage metric measurement, and basically fail a feature branch (short lived branch) if it decreases code coverage relative to the master branch. What would be the best way to achieve this, without writing a custom script that parses metrics from the API?

(Janos Gyerik) #2

The work on introducing real quality gates on pull requests is going to be released very soon, and I believe it will answer your need. Stay tuned!