![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
multijob-plugin |
|
Created:
|
13/Feb/15 2:16 AM
|
|
Description:
|
Currently when I have a multiple jobs running..
Instance of Main JOB 1
Subjob a (build number 1)
subjob b
subjob c
Instance of Main JOB 2
subjob a (build number 2)
subjob b
subjob c
Now if subjob a failed on the first Main Job, then it would attempt to retry that subjob a and get a DEAD executor, because it fails to overwrite $Jenkins_Home\Workspace\Job\MainJob\builds\2 because its currently in USE by Main Job 2 subjob a
Should be a straightforward fix, have the retry portion of the multijob plugin reread the nextbuildnumber file and consequently assign the build a number that is not currently in use.
I believe it currently just increments the previous failed job number by 1
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Leeam Dagan
|
|
|
|
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.
