Sonarqube Scanner 2.7 is ignoring the Server URL setting in Jenkins config when checking quality gate

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: sonar-plugin
    • None
    • Environment:
      Sonarqube scanner 2.7
      Jenkins 2.107.1 (docker)

      The Sonarqube scanner is ignoring theĀ Server URL parameter in the Jenkins config when querying Sonar for the quality gate status. It is using Sonar's own address instead.Ā 

      I have an IP address set in Jenkins (as the intranet DNS will not resolve there), whereas for users I have a friendly hostname set in Sonar. Jenkins tries to resolve the friendly hostname instead of theĀ Server URL I specify, which fails, and breaks the build.

      I've reverted back to 2.6.x for now.

            Assignee:
            Sonar Team
            Reporter:
            David Sanftenberg
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: