Coverage in master is not updating

[phil-davis]

Template for a good new topic, formatted with Markdown:

• ALM used - GitHub
• CI system used - drone
• Scanner command used when applicable - sonarsource/sonar-scanner-cli docker in drone build
• Languages of the repository - PHP and JavaScript
• URL - https://sonarcloud.io/code?id=owncloud_core
• PR - https://sonarcloud.io/dashboard?id=owncloud_core&pullRequest=37984

That PR is the first PR with SonarCloud coverage results to be merged. The PR calculated 55.2% coverage.

The PR has been merged, but the coverage reported in the “master” dashboard overview https://sonarcloud.io/dashboard?id=owncloud_core is still 0%

Note: we do not re-run our unit tests on PR merge. The tests were already run and passed in the PR.

How do we get the “master” coverage (and other analysis information) to update?

[phil-davis]

I made the unit tests run again in the merge CI, and do SonarCloud analysis…
Now there is coverage detail available at https://sonarcloud.io/component_measures?id=owncloud_core&metric=coverage&view=list
So I guess there is no magic - we have to run the tests again on merge.

[janos (Janos Gyerik)]

@phil-davis

So I guess there is no magic - we have to run the tests again on merge.

After the PR is merged to master, you must analyze master again to update the code quality measures for it. The test coverage report from the pull request is not remembered in any way, so you must provide that again to the new scan of master. No magic indeed!