Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18600

Can't send new jobs to Sonar after Sonar upgrade: Not authorized

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • sonar-plugin
    • None

      After upgrading the Sonar version to 3.5.1, news jobs that are created are unable to build due to:

      [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project XXXXX: Can not execute Sonar: Not authorized. Please check the properties sonar.login and sonar.password. ->

      The Jenkins jobs that existed prior to the upgrade, are working fine with Sonar.

          [JENKINS-18600] Can't send new jobs to Sonar after Sonar upgrade: Not authorized

          rabreu created issue -

          sbrandhof added a comment -

          It's the expected behavior.
          Please read http://docs.codehaus.org/display/SONAR/Release+3.4+Upgrade+Notes

          sbrandhof added a comment - It's the expected behavior. Please read http://docs.codehaus.org/display/SONAR/Release+3.4+Upgrade+Notes
          sbrandhof made changes -
          Assignee Original: Sonar Team [ sonarteam ] New: sbrandhof [ sbrandhof ]
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          sbrandhof made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

          rabreu added a comment -

          The username and password were already configured. The old jobs usem them successfull.

          rabreu added a comment - The username and password were already configured. The old jobs usem them successfull.

          sbrandhof added a comment -

          You should request the user mailing-list:
          http://www.sonarqube.org/get-support/

          Thanks

          sbrandhof added a comment - You should request the user mailing-list: http://www.sonarqube.org/get-support/ Thanks

          Bruno Medeiros added a comment -

          I had a similar problem, and it was a Sonar fault.

          My Sonar has a LDAP auth, and one non-LDAP user for Jenkins. At some Sonar upgrade, the non-LDAP user stopped working together with LDAP users, it gives me always auth error, that was why Jenkins Sonar Plugin also stopped working.
          If that is the case, you need to use sonar.security.localUsers, see http://sonarqube.15.x6.nabble.com/cannot-login-to-sonar-using-created-user-and-ldap-td5025428.html and http://jira.codehaus.org/browse/SONAR-4543.

          Bruno Medeiros added a comment - I had a similar problem, and it was a Sonar fault. My Sonar has a LDAP auth, and one non-LDAP user for Jenkins. At some Sonar upgrade, the non-LDAP user stopped working together with LDAP users, it gives me always auth error, that was why Jenkins Sonar Plugin also stopped working. If that is the case, you need to use sonar.security.localUsers, see http://sonarqube.15.x6.nabble.com/cannot-login-to-sonar-using-created-user-and-ldap-td5025428.html and http://jira.codehaus.org/browse/SONAR-4543 .
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 149910 ] New: JNJira + In-Review [ 206762 ]

            sbrandhof sbrandhof
            rabreu rabreu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: