[JIRA] [core] (JENKINS-16220) With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.

2014-10-17 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-16220


With Concurrent Builds enabled, faster builds wont fully complete until slower builds are done.
















Change By:


Daniel Beck
(17/Oct/14 12:42 PM)




Component/s:


postbuild-task



























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/d/optout.


[JIRA] [core] (JENKINS-16220) With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.

2014-10-17 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 resolved  JENKINS-16220 as Not A Defect


With Concurrent Builds enabled, faster builds wont fully complete until slower builds are done.
















The behavior you're seeing is deliberate by the configured post-build steps. For a long time, email sending (both Mailer and email-ext IIRC) blocked build completion because it wanted to make sure to use the correct subject ("Failed" vs. "Still Failing"). AFAIK this was changed, leading to potentially slightly wrong email subjects.

Unless the post-build steps are provided by core (and actually have no reason to wait), this is not a core bug, and more information on the job configuration is needed to investigate further. Separate issues should be filed against the responsible post-build action plugins so their authors can investigate further. Some post-build actions may well need this synchronization, while for others, it provides less value than faster build completion.





Change By:


Daniel Beck
(17/Oct/14 12:45 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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/d/optout.