Sonar Jenkins

Sonar Hudson plugin handling of alternate settings.xml is broken after changes in Hudson maven plugin

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.1
  • Fix Version/s: 1.7
  • Labels:
    None
  • Environment:
    Hudson 1.393
  • Number of attachments :
    0

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. SONARJNKNS-151 use same logic as maven-plugin to resolve alternate settings.xml

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Stevo Slavic added a comment -

This issue is related to SONARPLUGINS-326

Show
Stevo Slavic added a comment - This issue is related to SONARPLUGINS-326
Hide
Permalink
Stevo Slavic added a comment -

Related http://issues.jenkins-ci.org/browse/JENKINS-4693

Show
Stevo Slavic added a comment - Related http://issues.jenkins-ci.org/browse/JENKINS-4693
Hide
Permalink
Stevo Slavic added a comment -

Until this one is sorted out, instead of running sonar via hudson/jenkins sonar plugin I've configured m2 extra post-build step to run maven sonar plugin sonar goal with alternate settings.xml file passed with -s parameter by referencing WORKSPACE build variable in the path to build specific settings.xml file.

Show
Stevo Slavic added a comment - Until this one is sorted out, instead of running sonar via hudson/jenkins sonar plugin I've configured m2 extra post-build step to run maven sonar plugin sonar goal with alternate settings.xml file passed with -s parameter by referencing WORKSPACE build variable in the path to build specific settings.xml file.
Hide
Permalink
Stevo Slavic added a comment -

Since work has been started on this ticket, be aware of the bug Jenkins [1.426, 1.430] has, https://issues.jenkins-ci.org/browse/JENKINS-11004

So maybe best to use Jenkins 1.425 for testing the feature.

Show
Stevo Slavic added a comment - Since work has been started on this ticket, be aware of the bug Jenkins [1.426, 1.430] has, https://issues.jenkins-ci.org/browse/JENKINS-11004 So maybe best to use Jenkins 1.425 for testing the feature.
Hide
Permalink
Evgeny Mandrikov added a comment -

Note for myself : seems that JENKINS-4693 was fixed in Jenkins 1.378.

Show
Evgeny Mandrikov added a comment - Note for myself : seems that JENKINS-4693 was fixed in Jenkins 1.378.
Hide
Permalink
Evgeny Mandrikov added a comment -

I want to believe that this was fixed in 7188252.

Stevo Slavic, may I ask you to try plugin by building from sources in order to confirm that it works?

Show
Evgeny Mandrikov added a comment - I want to believe that this was fixed in 7188252 . Stevo Slavic, may I ask you to try plugin by building from sources in order to confirm that it works?
Hide
Permalink
Fabrice Bellingard added a comment -

Successfully tested on Jenkins stable version 1.409.2

Show
Fabrice Bellingard added a comment - Successfully tested on Jenkins stable version 1.409.2

People

  • Assignee:
    Evgeny Mandrikov
    Reporter:
    Stevo Slavic
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: