Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-12172

CI auto-configuration conflict with Jenkins

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.8
    • Component/s: Scanner
    • Labels:
      None
    • Edition:
      Community
    • Production Notes:
      None

      Description

      The CI auto-configuration fails if the env variable JENKINS_URL is defined on a non-Jenkins environment, for example in Bitbucket Pipelines in this thread.

      Jenkins does not offer a proper way to identify it. To reduce the risk of conflicts with other CI, both variables EXECUTOR_NUMBER and JENKINS_URL should be present to be sure that scanner runs on Jenkins. EXECUTOR_NUMBER should be standard and always set on Jenkins: https://wiki.jenkins.io/display/JENKINS/Building+a+software+project

        Attachments

          Activity

            People

            Assignee:
            simon.brandhof Simon Brandhof (Inactive)
            Reporter:
            simon.brandhof Simon Brandhof (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved: