I have a question about Pull Request Analysis of SonarQube Server.
I have been used SonarQube 7.4 Server version.
I want to integrate with jenkins and sonarQube as Pull Request Analysis.
(when pull request was received, sonarQube static analysis result can checked too,
The important thing is available before history analysis record)
Now I was composed with bitbucket - jenkins pull request auto build environment.
Next, I want to get sonarqube analysis result that analyze with corrected code as pull request.
At first, what I tried to archive was using branch analysis.
But branch analysis was reported about master(long term) only (maybe?).
I wanted to see the analysis result(I thank, itās available to SonarQube Activity tab.)
My purpose is checking the pull request levelās code analysis result history.
Is code analysis recording that corrected in pull request possible?
Can I get some information about this issue?
Thank you SonarQube!
Iāll waiting for your response
I have difficulty understanding what your question is. If youāre using PRs in your SCM, you should be able to configure your CI toolchain to automatically re-analyze each PR after each update to the underlying branch. If youāre not using PRs, then Short-lived branch analysis will give you many of the same features, tho not all.
What we want to do is want to see the history of performing the static analysis whenever PR comes along. I have estimated that this feature is available in SonarQubeās Activity tab.
However, even if a static analysis of the PR is actually performed, we have confirmed that the corresponding analysis history is not generated in SonarQube.
The SonarQube version we are currently using is 7.4. Is Pull Request Analysis support for Bitbucket possible? Provider registration exists only in Github and VSTS. Can the PR analysis function achieve our desired objectives?
In addition, Branch Analysis works normally, and the corresponding function is not up-to-date in the Activity Tab. Is it possible to update only the master branch? Or am I misunderstanding?
For reference, Jenkins performed the build using the SonarScanner for MSBuild tool.
Can I get more feedback on that?
Thank you for your kind reply.
Iāll try to handle whatās left after Carineās excellent answer.
This is correct. We donāt provide history for PRs and Short-Lived Branches under the assumption that what you care about for them is ānowā, and how many issues (for example) you had yesterday doesnāt matter. This is all about ācan I merge yet?ā and the fact that you could or couldnāt merge yesterday is irrelevant.
Sorry, youāre loosing me again here. When you analyze any given branch (short- or long-lived) that branch, and only that branch is updated in SonarQube.
