-
Bug
-
Resolution: Duplicate
-
Blocker
-
None
-
Platform: All, OS: All
I have created a single configuration project with "This build is parameterized"
option.
o VARIABLE NAME : FOO
o goto the shell script and echo $FOO;sleep 120
Now saved the configuration and started the build using following URL...
http://localhost:8080/job/buildWithParameters/buildWithParameters?FOO=TEST1
Now build #1 started.
While the build #1 is going on, I have started few more builds.
http://localhost:8080/job/buildWithParameters/buildWithParameters?FOO=TEST2
http://localhost:8080/job/buildWithParameters/buildWithParameters?FOO=TEST3
http://localhost:8080/job/buildWithParameters/buildWithParameters?FOO=TEST4
http://localhost:8080/job/buildWithParameters/buildWithParameters?FOO=TEST5
http://localhost:8080/job/buildWithParameters/buildWithParameters?FOO=TEST6
When the build #1 is completed, build #2 & build #3 are started together.
When the build #2 & #3 completed, build #4 & #5 are getting started together.
- duplicates
-
JENKINS-2997 multiple parallel parameterized builds seem to happen at once
-
- Resolved
-
Here is the scenario for multi configuration project:
o Currently the build is running for multi configuration project build #150
o I have submitted new build request through buildWithParameters and that
created build #151 in the Queue
(buildWithParameters?CHANGEID=95111&token=XXXXXXXXXXXXX).
o One more requested submitted through buildWithParameters and that created
build #152 in the Queue (buildWithParameters?CHANGEID=95112&token=XXXXXXXXXXXXX).
o Now the build #150 completed:
#151 & 152 together.
o #151: Within the few mins: Build #151 only executes master thread and the
marks the build as aborted but triggered all the slave process and they are
waiting in the Queue.
<log>
Triggering linux
Triggering windows
Triggering solaris
linux appears to be cancelled
windows appears to be cancelled
solaris appears to be cancelled
finished: ABORTED
</log>
O#152: Build #152 completes the master thread and starts the slave process.