sonarqube - Unable to Analyze trunk and branch in sonar Differential Views -


I have a huge codebase that I am analyzing through sonar. I have integrated sonar analysis in the CI creation process, and the current structure looks like this: --- product creation --- -Projectkey: ABC-Prod-project warsen: 2.0 - Project Name: ABC

Now, I have the process of running all our feature branches overnight (I do not want to change it for preview analysis and want full sonar for all) . This nightly branch analysis looks like this:

  --- Feature 1 --- - Project's key: ABC-Feature 1-Project Warson: 2.0.1 - Project Name: ABC - Fetcher 2 - - -Projectkey's: ABC-Feature2-Project Warsen: 2.0.2 -ProjectName: abc   

My question is: In this kind of structure, I get the difference between Prode Build and Feature Build I am not able to analyze. I know that there is a "compare" option to compare projects with different keys, but this is not enough for my case, because we want to see the exact new issues that have been added to the new features such as In protest against prod production.

Note: I can not use the same project key because

Can I reconstruct this anyway? I have dashboards that are always capable of pulling the latest analysis on every featured build along with the noise, and override the version numbers for the same projectcutter, updating the results everywhere in the final analysis results.

Any hint? Thanks!

I have to face the same problem, which I tried to use sonar's API First of all, enter the branch name and show the ID as "sonar.projectVersion" So you can use the API: Project / Index? Search = and version = All versions are correct to fetch.

Second: Set the Parma to see the difference to the sonar. If you can get the name of the branch in the final stage result, then set this kind of difference view Parma:

 < Code> & lt; Property name = "sonar.timemachine.period1" value = "latest version current branch" /> & Lt; Property name = "sonar.timemachine.period4" value = "latest version of current branch" /> & Lt; Property Name = "sonar.timemachine.period5" value = "latest version of current branch" />   

Otherwise you should compare the project to the original branch, such an inter-view Parma Set:

  & lt; Property name = "sonar.timemachine .period1" value = "parent branch comit id" /> & Lt; Property Name = "sonar.timemachine.period4" value = "parent branch.commit id" /> & Lt; Property Name = "sonar.timemachine.period5" value = "Basic Branch.com Id" />   

How to find the original branch: See, how to get the latest command id

Comments

Popular posts from this blog

c - Mpirun hangs when mpi send and recieve is put in a loop -

python - Apply coupon to a customer's subscription based on non-stripe related actions on the site -

java - Unable to get JDBC connection in Spring application to MySQL -