[JIRA] [git] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy

Fri, 04 Apr 2014 14:07:32 -0700

 
Mark Waite edited a comment on Bug JENKINS-22053

I confirmed that the null pointer exception is still visible in the log as of git-client-plugin 1.8.0 and git-plugin 2.2.0.

Started on Apr 4, 2014 2:49:22 PM
Polling SCM changes on master
Using strategy: Inverse
[poll] Last Built Revision: Revision 79b09609c1304a3db713c6a4f3bab0d46c85db56 (origin/master)
Fetching changes from the remote Git repositories
Fetching upstream changes from git://github.com/jenkinsci/git-client-plugin.git
Polling for changes in
ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@38b93a92[JENKINS-22053-inverse-build-strategy-npe]
java.lang.NullPointerException
	at hudson.plugins.git.util.InverseBuildChooser.getCandidateRevisions(InverseBuildChooser.java:45)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:535)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457)
	at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
	at hudson.scm.SCM.poll(SCM.java:373)
	at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1588)
	at hudson.model.AbstractProject._poll(AbstractProject.java:1558)
	at hudson.model.AbstractProject.poll(AbstractProject.java:1490)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468)
	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)



The work around (use a workspace for polling) is successful.  The root problem seems to be that the call to expand variable names needs the environment variables for a job, yet the environment variables for a job are only available when a workspace is available.
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to