| We switched our pipeline job generator to use DELTA for the quality gates instead of NEW. Now every new build pipeline fails the first (and every following) build until we reset the quality gate. This didn't happen with jobs that were generated with NEW. Shouldn't a first build automatically be accepted as the reference build no matter how many DELTA/NEW issues are detected? These are the final lines of the quality gate report (first build):
Evaluating quality gates
-> WARNING - Delta (any severity): 36 - Quality QualityGate: 1
-> FAILED - Delta of warnings (severity high): 1 - Quality QualityGate: 1
-> FAILED - Delta of warnings (severity normal): 6 - Quality QualityGate: 2
-> FAILED - Delta of warnings (severity low): 29 - Quality QualityGate: 4
-> Some quality gates have been missed: overall result is FAILED
Health report is disabled - skipping Output of the quality gate report of a different branch created earlier with "NEW" instead of "DELTA":
Evaluating quality gates
-> PASSED - Number of new warnings (severity high): 0 - Quality QualityGate: 1
-> PASSED - Number of new warnings (severity low): 0 - Quality QualityGate: 4
-> PASSED - Number of new warnings (severity normal): 0 - Quality QualityGate: 2
-> PASSED - Number of new issues (any severity): 0 - Quality QualityGate: 1
-> All quality gates have been passed
Health report is disabled - skipping |
