[JIRA] [core] (JENKINS-9913) Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent

[jgl...@cloudbees.com (JIRA)]

Jesse Glick updated JENKINS-9913 Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent Not a bug per se, but Jenkins needs to make sure that post-build actions which require the previous build to be complete (a) are documented to do so, e.g. in inline help; (b) print a helpful message to the build log when waiting for a previous build. And of course wherever feasible, offer an option to not block in this way, or to perform the processing dependent on the previous build asynchronously, e.g. in a RunListener. Change By: Jesse Glick (26/Jul/13 5:55 PM) Summary: Concurrent builds getting batched/nodes not getting released Not obvious why some post-build tasks enforce serial behavior even  when  jobs  builds  are  completed  concurrent Labels: concurrent-build junit Assignee: Kohsuke Kawaguchi Jesse Glick Priority: Blocker Major Component/s: core Component/s: concurrent-build

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.