Closed datasmurfen closed 6 years ago
Hi @datasmurfen, Can you elaborate about "Include Code coverage"? The problem with the quality gate is that is executed asynchronously and has not yet finished when sonar-stash is running. (This is also tracked in #95)
Also the quality gate is not run on preview runs (See #95)
Right, could it be possible to get the latest quality gate analysis from the "full" run(not the preview run)? Not sure if that would help, but it's one way to do it, I guess?
Well, it could be done, but it would be really confusing. I am strongly -1 on it.
Yea I agree, it would be very confusing.
Could you elaborate on the coverage you want to see? There is the coverage evolution plugin. It has a few caveats that are documented its README
I think it would been great to see if your pull request brakes/fix the current quality gate with an comment on what you break.
Must Have
Could have:
Ok, so it's also tied to the quality gate. As there is no quality gate available there is not much we can do. This will probably happen at all, because SonarSource is promoting their own (closed, paid) branch and pull request solution.
New Feature suggestion - Include code coverage, and alert if quality gate fail on pull request.
This is something I miss - today we use: https://github.com/kogitant/sonar-slack-notifier-plugin , but would be better to have this in one place.