-
Bug
-
Resolution: Fixed
-
Critical
-
None
Not sure what changed recently, but URL trigger started causing NullPointerExceptions whenever a job configuration change is attempted to be saved or applied:
Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.urltrigger.URLTrigger.getLogFile(URLTrigger.java:266) at org.jenkinsci.plugins.urltrigger.URLTrigger.getProjectActions(URLTrigger.java:108) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:188) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:464) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:460) at hudson.model.AbstractProject.save(AbstractProject.java:279) at hudson.model.AbstractItem.setDisplayName(AbstractItem.java:156) at hudson.model.Job.doConfigSubmit(Job.java:1044) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:765) at sun.reflect.GeneratedMethodAccessor670.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
The Jenkins version is 1.522 and URL trigger plugin is 0.29
In jenkins.log file the following errors are displayed:
Jul 10, 2013 12:26:12 AM org.jenkinsci.lib.xtrigger.AbstractTrigger run
SEVERE: Severe Error during the trigger execution null
java.lang.NullPointerException
at org.jenkinsci.plugins.urltrigger.URLTrigger.getLogFile(URLTrigger.java:266)
at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:128)
at hudson.triggers.Trigger.checkTriggers(Trigger.java:261)
at hudson.triggers.Trigger$Cron.doRun(Trigger.java:209)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
I verified that URL that URLTrigger is configured with is updated per check-in, so that's not an issue.
What other info do you need? This is blocking all snapshot builds (triggered thru URLTrigger) because they simply don't run anymore.
The attached screenshot shows the "Oops" error message:
This has same trace as shown in /var/log/jenkins/jenkins.log from my earlier comments
This configuration changes fail to be saved only in case of snapshot builds, where URLTrigger is used to fire off a build whenever a change is checked-in
If the build doesn't define URL trigger plugin in Build Triggers section, this error does not happen