|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [JIRA] (JENKINS-15324) email-ext static-an... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... slide.o....@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... hhu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) Aggregated maven re... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15324) Aggregated maven re... hhu...@gmail.com (JIRA)
My goal is to fail our build if there is new Finbugs error introduced into the code base and having the email reflects number of new errors that findbugs plugin found.
These are the options that are selected for the Finbugs plugin:
As a test, after a first run, the job passed since it's first ever run and no new findbugs errors found. The email showed Findbugs statistics just fine.
Then I intentionally checked in a Findbugs error to the one of my source class, the build ran and failed this time because Findbugs plugin saw the new warning threshold of 0 has been breached. Here is where the bug I filed came in: the email content of Findbugs statistics are all 0's (used to be empty strings). So you know that your build failed but you don't know that it failed because Findbugs found new errors. This email is quite vague to a developer.
Also, this bug only exposes when you use a Maven style job. A freestyle job generates the right content in the email when the build failed due to Findbugs.