Possibility to opt-out from pushing result to server

SonarQube Server / Community Build Product Manager for a Day
, , ,
1

Hi!

We are serving build templates and different flavours of build platforms to our users, and have the need to perform daily tests on both the SonarQube Extension tasks for Azure DevOps for msbuild and maven, and the scanner for standalone scans to quickly identify issues before our users, for example new releases of .NET core, JDK, Node, SQ extension tasks, the scanner.

For the automated test runs we use real applications in our environments for different languages, but we can not overwrite the results for the applications in SonarQube.

For this reason we would really benefit from a parameter to opt-out of pushing the result to SonarQube server.

This is a priority for us, as we have had 2 incidents caused by updates of the extension task within a pretty short time, and it is rather complex situation investigating as there are a dependency tree with SQ extension task updates → SQ scanner updates → SQ Server updates → JDK Updates etc.

2

Hey Patrik,

For test runs, we generally recommend using a separate SonarQube project key. This helps keep your test data isolated from production results.

Alternatively (or in combo), if you have access to a staging instance of SonarQube (available with the Enterprise Edition), that’s an ideal environment for running these tests.