![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
postbuildscript |
|
Created:
|
13/Feb/13 9:35 AM
|
|
Description:
|
If concurrent builds are enabled ("Execute concurrent builds if necessary" option) and the job is using postbuildscript plugin, then a build will wait for all the previous builds to finish before it completes.
As an example, say you have a job that sleeps a certain period and then uses postbuildscript to echo "hello world" with "Execute Windows Batch Command". If you now start three builds right after the other with parameters:
#1 sleeps 60s
#2 sleeps 30s
#3 sleeps 70s
You'll notice that builds #1 and #2 actually both take 60s to complete. Build #3 takes 70s. So build #2 waits for build #1 to finish.
|
|
Environment:
|
Tested with Jenkins 1.454 and 1.492 and postbuildscript 0.10
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Mikko Tapaninen
|
|
|
|
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.
