|
SonarQube branch analysis and Leak period
|
|
6
|
3777
|
April 6, 2024
|
|
Ratcheting Quality Gate conditions: Fail Quality Gate if coverage decreases from last analysis
|
|
26
|
4137
|
September 14, 2023
|
|
How to calculate coverage on new code even before pushing code to repository?
|
|
5
|
5058
|
March 6, 2022
|
|
AWS Code build + gradle
|
|
10
|
1598
|
August 12, 2021
|
|
Upcoming Changes to New Code Period
|
|
6
|
1134
|
August 19, 2020
|
|
New Code Coverage are Missing when Submit Code Earlier than Setting ‘sonar.leak.period=BASELINE’
|
|
5
|
1824
|
January 2, 2020
|
|
Leak Period Report Same As Overall Report
|
|
9
|
1345
|
January 31, 2019
|
|
How to make leak=overall
|
|
8
|
849
|
January 9, 2019
|
|
SonarQube Branch analysis / Leak Period
|
|
2
|
696
|
October 5, 2018
|
|
Sonar.leak.period being override
|
|
4
|
2683
|
October 2, 2018
|
|
Then a new code Leak Period in "Overview" tab, but no any change,redo analysis, Leak become 0
|
|
4
|
714
|
September 18, 2018
|
|
Newly code issue display with use leak periods
|
|
1
|
645
|
September 13, 2018
|
|
Leak period doesn't work for temporarily deleted files
|
|
3
|
1110
|
September 6, 2018
|
|
Negative values for issues in sonarqube webhook payload
|
|
4
|
965
|
September 3, 2018
|
|
How is SonarQube tracking and charging lines of code
|
|
11
|
14002
|
August 28, 2018
|
|
Over leak period....always
|
|
3
|
3357
|
August 22, 2018
|
|
Does "Some Quality Gate conditions on New Code were ignored because of the small number of New Lines" only appear at the beginning of a new leak period?
|
|
9
|
6162
|
August 20, 2018
|
|
Quality Gate condition to check number of issues decreased
|
|
2
|
2598
|
June 13, 2018
|