[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

[jya...@howlingduck.com (JIRA)]

Jim Yanko commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Went to: Manage Jenkins/Configure System/Extended E-mail Notification I set the override settings for Extended Email Notify as follows... [x] Override Global Settings SMTP server [ localhost ] Default user E-mail suffix [ hostname.env.domain.com ] System Admin E-mail Address [ us...@hostname.env.domain.com ] Notably, I set the override to use a diff acct name for the email address from the default by adding the '2' so I could confirm the override setting was being used to send the email. With Jenkins 1.493 (and email ext v 2.25) Ran a few builds of the sample job to force failure and success. Got emails from user2 address for each (indicates the override setting worked) Upgraded Jenkins to 1.498 (and email ext v 2.25) Ran a few builds of the sample job to force failure and success. each that should have sent email failed to send message for the status change ERROR: Could not send email as a part of the post-build publishers. Rolling back Jenkins to 1.493 (and email ext v 2.25) Ran a few builds of the sample job to force failure and success. Got emails from user2 address for each (indicates the override setting worked) Following is from the console log from the forced failure condition with Jenkins 1.498 installed... ... Starting the test @ Mon Jan 14 20:33:47 UTC 2013 (1358195627471) Waiting for possible shutdown message on port 4445 Tidying up ... @ Mon Jan 14 20:33:51 UTC 2013 (1358195631145) ... end of run Performance: Percentage of errors greater or equal than 5% sets the build as unstable Performance: Percentage of errors greater or equal than 10% sets the build as failure Performance: Recording JMeter reports '*.jtl' Performance: Parsing JMeter report file results.jtl Performance: File results.jtl reported 60.0% of errors [FAILURE]. Build status is: FAILURE Build step 'Publish Performance test result report' changed build result to FAILURE Recording fingerprints IRC notifier plugin: Sending notification to: #alerts Checking for post-build Performing post-build step Checking if email needs to be generated Email was triggered for: First Failure Trigger Success was overridden by another trigger and will not send an email. Sending email for trigger: First Failure Overriding default server settings, creating our own session ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:439) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:297) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1587) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Some error occured trying to send the email...check the Jenkins log Finished: FAILURE Just realized that I am seeing the following message each time I get back to version 1.493 when I go to the Manage Jenkins page. Is this significant to the issue at hand? Manage Jenkins You have data stored in an older format and/or unreadable data. New version of Jenkins (1.498) is available for download (changelog). Or Upgrade Automatically If I follow the manage link, it basically only gives me an option to 'discard unreadable data' and nothing else.

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