|
||||||||
|
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-16163) NullPointerException ... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcep... [email protected] (JIRA)

@Slide-O-Mix
I found some time today to look at this again...
Found and enabled debug in the global config for Jenkins.
I used a sample job that I could easily force to success or failure condition by resetting a timeout value.
This particular job was set to send an email on FIRST FAILURE and FIXED conditions.
Below is the console output from when the sample job came into FIXED status...