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

sonar runner configurations lost in jobs configurations since moved to 'global tools config' section

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • sonar-plugin
    • Jenkins 2.5
      sonarqube plugin 2.4.1

      In 1.x jenkins version, job build step 'launch analysis with SonarQube scanner' was saved with specified 'sonarQube scanner' (screenshot 1). This 'sonarqube scanner' install was declared in jenkins global configuration.

      Jenkins upgrade to version 2 has moved this configuration to 'global tools configuration' section (screenshot 2).

      Since this move, the list of available scanners is well populated when configuring the step but the 'sonarqube scanner' specified in job configuration is lost as soon as we save the job conf , then the sonar qube scanner build step becomes unusable.

      Is it possible to restore back this configuration to global jenkins configuration or to update the plugin so that we can use it from its new location ?

        1. 2016-05-19_0853.png
          2016-05-19_0853.png
          36 kB
        2. 2016-05-19_0856.png
          2016-05-19_0856.png
          45 kB
        3. 2016-06-03_1506.png
          2016-06-03_1506.png
          24 kB

          [JENKINS-34942] sonar runner configurations lost in jobs configurations since moved to 'global tools config' section

          Julien HENRY added a comment -

          Thanks for feedback. Release should be done by tomorrow.

          Julien HENRY added a comment - Thanks for feedback. Release should be done by tomorrow.

          Alexandre Aubert added a comment -

          Regression has been introduced with this fix, or the problem was also there and not yet detected : we have the same issue of conf not saved with the build step 'prepare sonarqube scanner analysis for MSBuild' . Could you please have a look ?
          Regards,

          Alexandre Aubert added a comment - Regression has been introduced with this fix, or the problem was also there and not yet detected : we have the same issue of conf not saved with the build step 'prepare sonarqube scanner analysis for MSBuild' . Could you please have a look ? Regards,

          Alexandre Aubert added a comment -

          same pb with different jenkins build step 'analysis for MSBuild'

          Alexandre Aubert added a comment - same pb with different jenkins build step 'analysis for MSBuild'

          Julien HENRY added a comment -

          Looking at the code it seems to be a similar issue introduced in 2.4. Ticket created: https://jira.sonarsource.com/browse/SONARJNKNS-255

          Julien HENRY added a comment - Looking at the code it seems to be a similar issue introduced in 2.4. Ticket created: https://jira.sonarsource.com/browse/SONARJNKNS-255

          Julien HENRY added a comment -

          splashnenen Could you please confirm the problem is fixed with this version: https://github.com/SonarSource/jenkins-sonar-plugin/releases/download/2.4.3-rc1/sonar.hpi

          Thanks!

          Julien HENRY added a comment - splashnenen Could you please confirm the problem is fixed with this version: https://github.com/SonarSource/jenkins-sonar-plugin/releases/download/2.4.3-rc1/sonar.hpi Thanks!

          Alexandre Aubert added a comment -

          checking

          Alexandre Aubert added a comment - checking

          Alexandre Aubert added a comment -

          I can confirm that both problems are well fixed in this version. thanks.

          Alexandre Aubert added a comment - I can confirm that both problems are well fixed in this version. thanks.

          Julien HENRY added a comment -

          Thanks, I will release 2.4.3.

          Julien HENRY added a comment - Thanks, I will release 2.4.3.

          Mikael Gaunin added a comment -

          This ticket should be closed, shouldn't it? (cf. SONARJNKNS-255)

          Mikael Gaunin added a comment - This ticket should be closed, shouldn't it? (cf. SONARJNKNS-255 )

          Alexandre Aubert added a comment -

          Indeed, this is well solved. My bad.

          Alexandre Aubert added a comment - Indeed, this is well solved. My bad.

            sonarteam Sonar Team
            splashnenen Alexandre Aubert
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: