Currently, the evaluation of new and fixed warnings is based on a reference build. I.e., as soon as a build gets unstable due to a warnings threshold being hit the job remains unstable until the new warnings are fixed.
Sometimes it make sense to reset the build status. I.e., the reference build should be removed so that in the next build the result will be stable.
|Field||Original Value||New Value|
|Issue Type||New Feature [ 2 ]||Improvement [ 4 ]|
|Assignee||Ulli Hafner [ drulli ]||tatura [ tatura ]|
|Assignee||tatura [ tatura ]||Ulli Hafner [ drulli ]|
|Workflow||JNJira [ 148028 ]||JNJira + In-Review [ 177066 ]|
|Remote Link||This issue links to "Page (Jenkins Wiki)" [ 17276 ]|
|Component/s||warnings-ng-plugin [ 24526 ]|
|Component/s||analysis-core-plugin [ 15709 ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Fixed but Unreleased [ 10203 ]|
|Released As||warnings-ng 2.2.0 (and analysis model 2.1.1)|
|Status||Fixed but Unreleased [ 10203 ]||Resolved [ 5 ]|