Sonar Jenkins

Hudson Job Sonar Link when a 'branch' property is specified

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.3, 1.2.2, 1.3.1
  • Fix Version/s: 1.4
  • Labels:
    None
  • Environment:
    RH Linux 5.1
  • Number of attachments :
    0

Description

On a Hudson project's homepage the Sonar link is supposed to take you to the project on the Sonar host. However if a branch is specified for the project (-Dbranch=1.3 for example) the link is invalid.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Kayhan Sefat added a comment -

Should really mention: Hudson 1.347, Sonar Plugin 1.2.2

Show
Kayhan Sefat added a comment - Should really mention: Hudson 1.347, Sonar Plugin 1.2.2
Hide
Permalink
Freddy Mallet added a comment -

Let's take a simple example :

the trunk of "ProjectA" (groupId=groupA and artifactId=artifactA) is daily analysed (mvn sonar:sonar) and the Sonar project dashboard is so available at given URL : http://localhost:9000/project/index/groupA:artifactA

One day, a branch is created and this branch is also placed under quality control. As the branch shares the same groupId:artifactId with the trunk, the sonar property "sonar.branch" is used to get two different projects in Sonar (mvn sonar:sonar -Dsonar.branch=1.2). The second project is so available at given URL : http://localhost:9000/project/index/groupA:artifactA-1.2

If the second case, the Hudson Job Sonar link is http://localhost:9000/project/index/groupA:artifactA and not the expected one http://localhost:9000/project/index/groupA:artifactA-1.2.

Show
Freddy Mallet added a comment - Let's take a simple example : the trunk of "ProjectA" (groupId=groupA and artifactId=artifactA) is daily analysed (mvn sonar:sonar) and the Sonar project dashboard is so available at given URL : http://localhost:9000/project/index/groupA:artifactA One day, a branch is created and this branch is also placed under quality control. As the branch shares the same groupId:artifactId with the trunk, the sonar property "sonar.branch" is used to get two different projects in Sonar (mvn sonar:sonar -Dsonar.branch=1.2). The second project is so available at given URL : http://localhost:9000/project/index/groupA:artifactA-1.2 If the second case, the Hudson Job Sonar link is http://localhost:9000/project/index/groupA:artifactA and not the expected one http://localhost:9000/project/index/groupA:artifactA-1.2 .
Hide
Permalink
Simon Brandhof added a comment -

Yes Freddy, that's it. Just a small rectification : the id is groupId:artifactId:branch, for example http://localhost:9000/project/index/groupA:artifactA:1.2

Show
Simon Brandhof added a comment - Yes Freddy, that's it. Just a small rectification : the id is groupId:artifactId:branch, for example http://localhost:9000/project/index/groupA:artifactA:1.2
Hide
Permalink
Evgeny Mandrikov added a comment -

Ok, I understand.

There is two ways how it can be implemented:

  • Add parameter branch to job configuration
  • Somehow handle "-Dsonar.branch" option

I prefer first way and it looks simple for implementation.
What do you think, guys?

Show
Evgeny Mandrikov added a comment - Ok, I understand. There is two ways how it can be implemented: Add parameter branch to job configuration Somehow handle "-Dsonar.branch" option I prefer first way and it looks simple for implementation. What do you think, guys?
Hide
Permalink
Freddy Mallet added a comment -

+1 for the first option !

Show
Freddy Mallet added a comment - +1 for the first option !
Hide
Permalink
Evgeny Mandrikov added a comment -

Done.
In order to use it: remove "-Dsonar.branch" from additional properties and use new configuration option.

Show
Evgeny Mandrikov added a comment - Done. In order to use it: remove "-Dsonar.branch" from additional properties and use new configuration option.

People

  • Assignee:
    Evgeny Mandrikov
    Reporter:
    Kayhan Sefat
Vote (2)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: