-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows 7 64bit. Jenkins 1.486.
Hi there,
I installed the new workspace cleanup plugin because I needed the fix for https://issues.jenkins-ci.org/browse/JENKINS-14128 but it seems the new version has caused another issue.
I have a matrix project which upon completion triggers a parameterized build on another project. The last thing in my job config is to delete the workspace when the build is done and I've ticked the box to clean the workspace of the matrix parent.
Checking the logs for my job, it looks like the downstream job is being called twice. Eg.
10:29:40 DebugOpt,GCC,2010,SlaveBuild4 completed with result SUCCESS 10:29:40 DebugOpt,x64Tool,2010,SlaveBuild4 completed with result SUCCESS 10:29:40 DebugOpt,x64D3D11,2010,SlaveBuild4 completed with result SUCCESS 10:29:40 DebugOpt,x64GL,2010,SlaveBuild4 completed with result SUCCESS 10:29:40 DebugOpt,Win32D3D11,2010,SlaveBuild4 completed with result SUCCESS 10:32:00 DebugOpt,Win32GL,2010,SlaveBuild4 completed with result SUCCESS 10:32:00 Triggering a new build of PerforceAutoCheckIn #364 10:32:00 10:32:00 Deleting matrix project workspace... 10:32:06 done 10:32:06 10:32:06 Triggering a new build of PerforceAutoCheckIn #365 10:32:06 Notifying upstream projects of job completion 10:32:06 Finished: SUCCESS
As you can see the downstream job ("PerforceAutoCheckIn") is being called twice.
Can this be fixed please?
Regards,
Tom