|
||||||||
|
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/groups/opt_out.
I have three slaves and each of them have multiple executors. There's two different jobs which both allocate a port with name ARQUILLIAN. Both of these jobs have concurrent builds.
Now only one build gets executed at a time, leaving other slaves and executors unused. Other builds stay in the queue with text "Blocked by <running build>". When the running build is completed, next one starts.
At some times, multiple builds are assigned to executors, but only one of them is actually running. Others are just waiting with empty consoles.
So, answers to your questions:
Do the queued builds continue once the build holding the blocked port has completed?
Yes, they do
Is a build on one slave being blocked because a port is being used on another slave?
Yes
Do you have a use case where you need all of the slaves to start running but then block during the build?
No, I just need one random port assigned to one job.