CODEWITHSUNDEEP
mavensonarqube
user3272389
user3272389

Reputation: 101

running maven sonar:sonar on multiple branches of the same source project

We currently have multiple feature releases in perforce. Each of these branches has POM files that contain a version tag and name tag that is tied to that branch.

When we run sonar:sonar each branch scan overwrites another branch scan and you only see one at a time in the sonar gui.

Can a sonar project be tied to maven GroupId>ArtifactId>Version or even instead of just being Tied to the GroupId.

FYI, GroupId and ArtifactId do not change when we branch the POM.

Upvotes: 10

Views: 3627

Answers (1)

user3704176
user3704176

Reputation: 111

I found your question while searching for a similar topic, and I noticed you had not received an answer. If you pass the -Dsonar.branch, each branch will be treated as a different project. As documented here:

http://sonarqube.15.x6.nabble.com/Sonar-Analysis-for-Feature-Branches-td5004642.html#a5004647

Hope this helps.

Upvotes: 11

Related Questions