We’re on the Developer Edition Version 9.9 (build 65466).
We’ve recently been looking at pull request analysis, as it has a more reliable analysis for direct merges rather than defining a reference branch to compare to.
However we’ve noticed an issue, or at least are unable to find any supporting documentation around the Quality Gate Ignore Small Changes configuration.
We have this setting turned on (default setting), which is what we desire, however it is only being applied or triggered during pull request analysis (where sonar.branch.name is not configured), and never by branch analysis, which results in false positive’s and failures occurring after merging.
See below the branch analysis in question, 7 lines of new code (below the threshold of 20), yet the quality gate fails, and the ignore small changes configuration is not being applied. (The info banner is not showing)
See below the pull request analysis in question, exact same branch, just 6 lines of new code (below the threshold of 20), now in this scenario the ignore small changes configuration is being applied as it’s intended purpose. (The info banner is showing)
The problem now arises where the quality gate has passed on our pull request, me merge our code, then main branch runs, and subsequently fails the quality gate in the same fashion as the branch analysis, due to the ignore small changes configuration not kicking in for the branch.
Should the ignore small changes configuration apply to all types of analysis? If yes, why is this not occurring in this scenario, is there another supporting setting or are we missing something else?
Have I misunderstood the ignore small changes configuration? Nothing in it mentions anything specific to only pull requests.
Can someone explain the purpose of this configuration in detail, and why it applies in one scenario and not another, as this is quite infuriating causing a misrepresentation of the analysis.