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, send email to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to