This is related to the fix for JENKINS-11255. That change blocks makes the build queue rather than just block mid-build waiting for a port to become available.

It is not clear to me from your report what problem this is causing you.

  • Do the queued builds continue once the build holding the blocked port has completed?
  • Is a build on one slave being blocked because a port is being used on another slave?
  • Do you have a use case where you need all of the slaves to start running but then block during the build?

I would help greatly if you could describe a simple test case that allows your problem to be reproduced/tested.

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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to