SonarQube 8.2 Branch Regression?

SonarQube Server / Community Build
1

We see a major regression after updating from 7.9.1 LTS to 8.2
We use Sonarqube to analyze the master branch, feature branches derived from it and pull requests.

With 8.2 there is the problem that sonar issues that are introduced and closed on master appear in the feature branch analysis when the feature branch merges the actual master.
Same for Security Hotspot review.
Also the other direction does not work.
Closing Security Hotspot review in feature branch, but they reappear on master after merging.

This kills our whole branching workflow

1 Like
2

I’ve moved your post to a new topic.

3

Hi,

I’m confused. Could you give some more detail about the process here?

 
Ann

5

Here is the procedure we follow:

  1. Development on new code in feature branch feature/A that introduces sonar issues
  2. Run sonar analysis on feature/A and close issues in sonarqube
  3. Create Pull Request and run sonar analysis on pull request merged with master
  4. Problem1: Closed issues reappear in sonarqube, but this is the case with every sonarqube version.
  5. Close issues again on PR and merge to master
  6. Problem2: Issues reappear on master
  7. Close issues on master again
  8. Developer merges master into other feature branch feature/B
  9. Problem3: Run sonar analysis on feature/B and issues appear again
6

Hi,

When you “Close” in #5, I guess we’re talking about FP/WF?

And in #8, is DeveloperB touching the same code that DeveloperA touched?

 
Ann

7

Hi

in 5# yes they are closed as False Positive or Wont Fix.
in 8# DeveloperB is not touching the same code but gets the issues from DeveloperA again.

Kind regards,
Michael

1 Like
9

Please let me know if you need further input for reproducing the issue. This is really a show stopper actually

1 Like