|
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
| Powered by Nabble | Edit this page |

I also have this issue, however, I discovered that the job I'm running is being run the correct number of times but in parallel rather than sequentially.
For my Multi-Job I have 4 phases; the first 3 phases are to run the same build job but with different prameters (solutions). The fourth phase is to run a deployment step.
When I run the multi-job, the first 3 phases run simultaneously although it looks like just one run. Luckily I spotted that when first looking at the console it was run #18 but when returning after completion it was #20. When I manually look at each #18, #19 & #20, I can see they are in fact the the three phases.
Jenkins: V1.491
Multi-Job plugin: V1.7