-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
Jenkins 1.502
Polling on master node fails with message:
Inspecting Monitor a change of the content content for URL ${JENKINS_URL}job/Commit/lastStableBuild/buildNumber
Polling started on Mar 11, 2013 1:00:10 AM
Polling for the job Functional_SV900
Looking nodes where the poll can be run.
Looking for a node to the restricted label master.
Can't find any eligible nodes.
Trying to poll on master node.
Polling on master.
[ERROR] - SEVERE - Polling error null
Stack trace (from Jenkins/Tomcat log file)
java.lang.NullPointerException
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.gatherEnvVarsNode(EnvVarsResolver.java:160)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getDefaultEnvVarsJob(EnvVarsResolver.java:89)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:68)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:36)
at org.jenkinsci.plugins.urltrigger.URLTrigger.getURLValue(URLTrigger.java:108)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModifiedEntry(URLTrigger.java:136)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModified(URLTrigger.java:125)
at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:197)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[JENKINS-17145] URLTrigger gives severe error message, envinject NPE
Gregory Boissinot
added a comment - It seems to be due to an offline node.
Does your nodes go offline?
Gregory Boissinot
added a comment - It seems to be due to an offline node.
Does your nodes go offline? 
dmeibusch
added a comment - Yes, some of our nodes do go offline.
However, I've configured this polling to always run on the master.
dmeibusch
added a comment - Yes, some of our nodes do go offline.
However, I've configured this polling to always run on the master. Gregory Boissinot
added a comment - Could you try with the last version (0.28)? dmeibusch
added a comment - This is with version 0.28. Gregory Boissinot
added a comment - Please could you add again the stacktrace with URLTrigger 0.28?
It seems your posted strack trace doesn't match the version and therefore I cannot try to identify the right error.
Thanks
Gregory Boissinot
added a comment - Please could you add again the stacktrace with URLTrigger 0.28?
It seems your posted strack trace doesn't match the version and therefore I cannot try to identify the right error.
Thanks dmeibusch
added a comment - Just confirming, Jenkins reports that we have v0.28.
Stack trace look pretty similar to above. 
Almost 100% sure now that we only see this exception when our slaves are idled down.
java.lang.NullPointerException
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.gatherEnvVarsNode(EnvVarsResolver.java:160)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getDefaultEnvVarsJob(EnvVarsResolver.java:89)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:68)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:36)
at org.jenkinsci.plugins.urltrigger.URLTrigger.getURLValue(URLTrigger.java:108)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModifiedEntry(URLTrigger.java:136)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModified(URLTrigger.java:125)
at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:197)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
dmeibusch
added a comment - Just confirming, Jenkins reports that we have v0.28.
Stack trace look pretty similar to above.
Almost 100% sure now that we only see this exception when our slaves are idled down.
java.lang.NullPointerException
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.gatherEnvVarsNode(EnvVarsResolver.java:160)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getDefaultEnvVarsJob(EnvVarsResolver.java:89)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:68)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:36)
at org.jenkinsci.plugins.urltrigger.URLTrigger.getURLValue(URLTrigger.java:108)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModifiedEntry(URLTrigger.java:136)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModified(URLTrigger.java:125)
at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:197)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Gregory Boissinot
added a comment - Please test urltrigger from 0.31
It should be fixed for now.
Thanks
Gregory Boissinot
added a comment - Please test urltrigger from 0.31
It should be fixed for now.
Thanks 
This looks similar to
JENKINS-16774, with a different stack trace (more recent version of plugin, 0.28).We have many jobs configured very similarly to this (same polling URL). Some fail to poll, others do not, others do occasionally - can't see any differences in job or execution to explain this.