-
Bug
-
Resolution: Fixed
-
Blocker
-
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 ?
[JENKINS-34942] sonar runner configurations lost in jobs configurations since moved to 'global tools config' section
Alexandre Aubert
created issue -
Julien HENRY
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Julien HENRY
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Julien HENRY
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Alexandre Aubert
made changes -
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Alexandre Aubert
made changes -
| Attachment | New: 2016-06-03_1506.png [ 32901 ] |
| Workflow | Original: JNJira [ 171144 ] | New: JNJira + In-Review [ 186367 ] |
Alexandre Aubert
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
