This might be a workspace locking issue as the polling log you post seems to indicate that the polling has started [1], but has not completed. even though the concurrent is allowed.
Try adding a logger for hudson.slaves.WorkspaceList to the log page and see if there is a log message <Some Threadname:> " acquired <workspacepath>" occurring just after the first build finishes, which would indicate that this is the case. Here is the detailed bit if you want to know more! and take some thread dumps to prove that the polling thread is "Waiting to acquire <workspace being used by the active build>" >From the code in the git plugin it looks like the polling requires a workspace [2] and during the poll code in AbstractProject it tries to lock the lastbuild's workspace to do this [3]. However this looks like it may block if the last build is the one that is building, due to different context in the acquire and allocate calls from AbstractProject and AbstractBuild [4] called on WorkspaceList [5]. Chris [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/triggers/SCMTrigger.java#L438 [2] https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L635 [3] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L1475 [4] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractBuild.java#L558 [5] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/slaves/WorkspaceList.java#L221 On Monday, 28 January 2013 21:56:31 UTC, skymoo wrote: > > Hi > > One of my Jenkins projects is configured to poll git and trigger a new > build if appropriate by using a post-receive hook and the Git Plugin. > > This specific project has two build slaves which can build the project > but it seems that if a single build is already in progress, with one > slave idle, and a change comes in that should trigger a new build it > isn't started until the running build has completed. No job enters the > queue and the "Git Polling Log" simply states something along the > lines of: > > Started on Jan 28, 2013 3:39:44 PM > > When the currently running job has completed polling with complete and > a job will be scheduled. The project is configured to "Execute > concurrent builds if necessary". I would expect that as a build slave > is available that another build would enter the queue and be assigned > to this idle node. I can manually schedule a job but I would like the > post-receive hook to be able to trigger a build if a node is > available. > > Am I misunderstanding the "Execute concurrent builds if necessary" > option, or do I have some kind of misconfiguration somewhere? > > Cheers > > Adam > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
