Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
email-ext 2.24.1, jenkins 1.483, findbugs plugin 4.44, Static Analysis Utilities 1.47
Description
Maven aggregation results are not computed if the build failed during a maven module (due to a threshold being hit). I.e., the build creates a maven module result with status failure. However, the aggregation action on job level does not show these results.
Attachments
Issue Links
- is related to
-
-
- Resolved
-
Activity
Ok, I see. Then the problem is not in email only. It is in the internal logic of the maven code: the aggregating action is not created when the build failed in a maven module.
Until this is fixed you can use as a workaround the unstable thresholds and not the failed ones (i.e. a warning sets the build to unstable). Alternatively, as you already described use the freestyle project.
hhuynh
added a comment - Thank you. I'm glad we got some root cause of it. I've tried unstable thresholds and it's not quite working right either. HIGH, NORMAL and LOW counts are there but not the NEW or FIXED counts (still 0).
I've used these calls:
${action.result.getNumberOfFixedWarnings()}
${action.result.getNumberOfNewWarnings()}
which are available in class hudson.plugins.findbugs.FindBugsReporterResult (which is ${action.result.getClass()})
I can't use freestyle jobs unfortunately because we're relying on Maven dependencies fingerprints for our upstream/downstream relationships (we have a lot of projects)
hhuynh
added a comment - Thank you. I'm glad we got some root cause of it. I've tried unstable thresholds and it's not quite working right either. HIGH, NORMAL and LOW counts are there but not the NEW or FIXED counts (still 0).
I've used these calls:
${action.result.getNumberOfFixedWarnings()}
${action.result.getNumberOfNewWarnings()}
which are available in class hudson.plugins.findbugs.FindBugsReporterResult (which is ${action.result.getClass()})
I can't use freestyle jobs unfortunately because we're relying on Maven dependencies fingerprints for our upstream/downstream relationships (we have a lot of projects)
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/analysis/core/MavenResultAction.java
http://jenkins-ci.org/commit/analysis-core-plugin/b506c418b4b3579d7cb71f31498cdbc21bbfc618
Log:
[FIXED JENKINS-15324] Aggregate build results if a failed build is
caused by a plugin threshold.
–
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Integrated in 
Jenkins Analysis Plug-ins (Compile) #609
[FIXED JENKINS-15324] Aggregate build results if a failed build is (Revision b506c418b4b3579d7cb71f31498cdbc21bbfc618)
Result = SUCCESS
I rerun it and took the a closer look and realized both Findbugs Warnings and Static Analysis Warnings disappeared after the failed run. I had to refresh the page to see that (otherwise, it would look like they're still there but they're actually links from successful build earlier). Screenshot attached. I have a temporarily instance of Jenkins running here http://173.167.103.153:8080