|
I encountered a situation where a single workspace is used by two concurrent builds.
The job is configured as follows:
(checked) Execute concurrent builds if necessary
(unchecked) Use custom workspace
(checked) This build is parameterized
I see the following builds:
Failed Build #66 (Jun 19, 2012 1:38:56 AM) (on slave 1), Took 4 min 3 sec
Success Build #67 (Jun 19, 2012 1:40:51 AM) (on slave 2), Took 14 min
Failed Build #68 (Jun 19, 2012 1:43:00 AM) (on slave 1), Took 3 min 14 sec
#66 shows:
Started by upstream project "OTHERNAME" build number 18
Building remotely on slave1 in workspace /var/lib/jenkins/workspace/NAME
Checkout:NAME / /var/lib/jenkins/workspace/NAME - hudson.remoting.Channel@7a85a2cf:slave1
#68 shows:
Started by upstream project "YETANOTHERNAME" build number 13
Building remotely on slave1 in workspace /var/lib/jenkins/workspace/NAME
Checkout:NAME / /var/lib/jenkins/workspace/NAME - hudson.remoting.Channel@7a85a2cf:slave1
The builds for this job are triggered by several upstream jobs. Each build should be able to run in parallel and the job is parameterized by a git branch (#66, #67 and #68 worked on different branches).
As soon as #68 started (and cleaning its workspace, so cleaning also the workspace of #66), #66 crashed.
Please tell me if you need more information!
|
