SonarQube 7.8 is used in our bitbucket pipeline and fails all our builds

Template for a good bug report, formatted with Markdown:

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)
[INFO] Bitbucket Cloud Pipelines detected
[INFO] User cache: /root/.sonar/cache
[INFO] SonarQube version: 7.8.0
  • error observed (wrap logs/code around triple quote ``` for proper formatting)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 39.677 s
[INFO] Finished at: 2019-06-04T06:14:36Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin: (default-cli) on project amnis-parent: Multiple CI environments are detected: [Bitbucket Pipelines, Jenkins]. Please check environment variables or set property to true. -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]
  • steps to reproduce
    run npm sonarscanner or mvn sonar command

  • potential workaround

P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour

the suggested fix didn’t solve the problem.

The problem first occured yesterday 15:55

Hi Egbert,

Is the env variable JENKINS_URL defined on your Bitbucket pipeline build?

Yes the Jenkins_URL globally configured

Ok, thanks for the information.
The fix SONAR-12172 will be deployed as soon as possible. It should resolve your problem if your Bitbucket job does not set the env variable EXECUTOR_NUMBER too!

1 Like

@egbert.bleeker fix has been deployed. Could you please validate that everything is back to normal?
Thanks in advance.

1 Like

yes the fix worked.

Thanks for the quick fixing of this issue

1 Like