Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Trivial
-
Resolution: Fixed
-
Component/s: findbugs-plugin
-
Labels:None
-
Similar Issues:
Description
Provide a better description of the "Only use stable builds as reference" option. See comments for details.
Attachments
![Trunk_BuildInstaller Config [Jenkins]_2014-08-15_16-54-12.jpg](/secure/attachment/26536/Trunk_BuildInstaller%20Config%20%5BJenkins%5D_2014-08-15_16-54-12.jpg)
Issue Links
- duplicates
-
JENKINS-13458 Add switch to set reference build always as the latest build
-
- Resolved
-
Activity
sounds great, thanks.
Markus Schlegel
added a comment - sounds great, thanks. Ok, I changed the title and description.
JENKINS-13458 is kind of what I was looking for, if specific to FindBugs (means setting the flag for findbugs does not set it for all others too).
I voted for it.
Maybe the tooltip on the flag "Only use stable builds as reference" could better reflect the current behavior.
Markus Schlegel
added a comment - JENKINS-13458 is kind of what I was looking for, if specific to FindBugs (means setting the flag for findbugs does not set it for all others too).
I voted for it.
Maybe the tooltip on the flag "Only use stable builds as reference" could better reflect the current behavior. This option only applies to builds that are unstable due to test failures. It is not influenced by the unstable result of the findbugs plug-in. A reference build is always the build that is successful (with respect to the findbugs plugin).
If a warning is acceptable then you should mark it with @SuppressWarnings annotation.
Or is JENKINS-13458 something you are actually looking for?
In the past few years, we had not set the threshold for the low priority issue. But due to a reorganisation, we now wanted to enable email notification for the developers which checked in also for these low-priority issues of Findbugs.
Therefore we set the threshold such that every new low priority issue will result in an unstable build. So far so good.
But sometimes, these low priority issues are just ok and we do not want the build be unstable forever.
We would like that developers gain ONE email notification when the warning appeared the first time and not after every subsequent build.
Therefore I thought that unchecking the setting "Only use stable builds as reference" should result in exactly that. Every subsequent build should calculate the number of new warnings from the last build (also from an unstable) and not the last stable one.
Markus Schlegel
added a comment - In the past few years, we had not set the threshold for the low priority issue. But due to a reorganisation, we now wanted to enable email notification for the developers which checked in also for these low-priority issues of Findbugs.
Therefore we set the threshold such that every new low priority issue will result in an unstable build. So far so good.
But sometimes, these low priority issues are just ok and we do not want the build be unstable forever.
We would like that developers gain ONE email notification when the warning appeared the first time and not after every subsequent build.
Therefore I thought that unchecking the setting "Only use stable builds as reference" should result in exactly that. Every subsequent build should calculate the number of new warnings from the last build (also from an unstable) and not the last stable one. Can you please add more details what you tried?
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/resources/util/thresholds.properties
src/main/resources/util/thresholds_de.properties
http://jenkins-ci.org/commit/analysis-core-plugin/c7d39361c6f38b4d93dbf502e616499cf942524b
Log:
[FIXED JENKINS-24289] Improved doc of stableReferenceBuilds.