SonarQube Scanner for Jenkins: suppress report-task.txt warning

This is fairly similar to I tried raising an issue on that Jira, but don’t seem to have permissions.

We use withSonarQubeEnv to obtain credentials that are then used in calls to the Sonar Web API: this is unconnected to any use of the scanner. Unfortunately, doing this results in a warning in the Jenkins logs:

WARN: Unable to locate ‘report-task.txt’ in the workspace. Did the SonarScanner succedeed?

This is just noise (not to mention the typo! Presumably it should say “Did the SonarScanner succeed?”) and can be confusing for users. Is there a way to suppress this in pipelines where no report file is expected or desired?

We have the same problem. I’ve tried to explain to devs it’s just noise but I get a new problem opened weekly from someone thinking their Sonar scan didn’t run.

It does seem like this could be a really small change, something like:


Just to let you know that an initial version of this has been merged through
No release plan yet, but it is coming.


1 Like

Great news, thanks! I’d had an eye on that ticket. Just out of curiosity, how does the release process work? The last tag in that repo is 2.3 from 2015, whilst the forked repo at has a 2.11 tag from January this year, but no commits since then.