Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
Windows CP, Git 1.1 Hudson 1.377
Description
I get the following error when using the latest git plugin.
This prevents any build from starting
Started on Sep 23, 2010 9:03:14 AM
Using strategy: Default
[poll] Last Build : #539
[poll] Last Built Revision: Revision 1202a30ee369bd0ee69c006a20e4cc4d1e91e8ba (origin/master)
ERROR: Failed to record SCM polling
[8mha:AAAAWB+LCAAAAAAAAABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=[0mjava.lang.NullPointerException
at hudson.model.Run.getEnvironment(Run.java:1673)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:682)
at hudson.plugins.git.GitSCM.pollChanges(GitSCM.java:420)
at hudson.scm.SCM.poll(SCM.java:369)
at hudson.model.AbstractProject.poll(AbstractProject.java:1195)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:355)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:384)
at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Attachments
Issue Links
- is related to
-
-
- Resolved
-
Activity
Integrated in 
plugins_hudson-git-plugin #28
JENKINS-7547 Fixed the problem with polling failing if the master has 0 executors but I'm having trouble getting 0 executors on master in unit tests
Andrew Bayer :
Files :
- src/test/java/hudson/plugins/git/GitSCMTest.java
- src/main/java/hudson/plugins/git/util/GitUtils.java
- src/main/java/hudson/plugins/git/GitSCM.java
OK. Well for my part I rolledback to 1.0.1 and all works fine again. There is nothing that I badly needed in 1.1 so I will wait for a fix to this problem before upgrading again. I really don't want to have executors on the master.
Ah-ha - this is the same underlying problem as JENKINS-6126 - it only shows up if the master has 0 executors. So one workaround for now is to just enable 1 executor on the master, if you can - I'll try to figure out a way to fix the real problem.
For what it's worth, what's confusing me here is that the change that's relevant here is one that's used in other plugins, such as the Mercurial plugin - we're just calling getEnvironment on the last build of the project, and in fact, we only get that far if there's been an earlier build in the first place.
This is strange - I can't seem to recreate it so far. Is this happening with the build on master or slave?
ieure
added a comment - Also ran into this today, after upgrading to GitSCM 1.1 yesterday. Manual builds work fine, but polling is broken.
ieure
added a comment - Also ran into this today, after upgrading to GitSCM 1.1 yesterday. Manual builds work fine, but polling is broken. Same here, this is critical. I am getting the same problem on windows and on Linux.
The issue seems to be resolved using the git.hpi found on http://ci.hudson-labs.org/job/plugins_hudson-git-plugin/28/org.jvnet.hudson.plugins$git/ .
Thank u for your quick response.