Hi, I am using Azure Pipelines with the Maven3 task and setting code coverage and sonarcloud analysis. Analysis and code coverage reports are bing uploaded to SonarCloud BUT maven is actually being run twice and increasing our build times more than we would like.
Basically maven runs our package, verify or deploy task and as soon as it completes another maven command is run with the jacoco agent being present and runs a second clean and verify. We have confirmed that this happens when code coverage is enabled in the maven task and the second build is not triggered when code coverage is not enabled.
We had thought that we could add the jacoco agent to the main maven task however when we do this NO COVERAGE is reported to SonarCloud.
Is this a bug? Is anyone aware of a workaround?
Thanks, Andy.