[JIRA] (JENKINS-13939) Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done

[vjura...@java.net (JIRA)]

vjuranek
 commented on  JENKINS-13939


Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done















Hi, this seems to me as a problem of ordering post build actions. This should be fixed in Jenkins 1.463 where use can order post build actions himself (while before it was hard coded number in plugin, which could cause exactly the issue you've described). Could you please test with Jenkins 1.463 or later if it's really fixed or not? Thanks.



























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

[JIRA] (JENKINS-13939) Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done

[jswa...@alohaoi.com (JIRA)]

Jason Swager
 commented on  JENKINS-13939


Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done















Could this be related to JENKINS-15236?  Perhaps the failures in workspace cleanups is because another job (or another build of the same job) started running in the same workspace before the current job had a chance to cleanup?



























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

[JIRA] (JENKINS-13939) Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done

[bsl...@gmail.com (JIRA)]

Ben Sluis created JENKINS-13939:
---

 Summary: Workspace cleanup plugin causes Jenkins to consider a job 
as completed before it is actually done
 Key: JENKINS-13939
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13939
 Project: Jenkins
  Issue Type: Bug
  Components: ws-cleanup
Affects Versions: current
 Environment: Windows Server 2008
Reporter: Ben Sluis
Assignee: vjuranek
 Attachments: BuildSteps.png

The latest version (0.8) of the workspace cleanup plugin seems to cause Jenkins 
to think a job is complete before it actually finishes all post build steps.  
Going back to version 0.7 doesn't show this problem.

Example:  See attached BuildSteps.png
'Results' is a job that blocks when upstream jobs are running.  Jobs A, B, C, 
and D trigger the downstream job 'Results' and pass their current build 
parameters (which are all the same) using the Parameterized Trigger plugin 
(v2.14).
In the scenario where only one upstream job is still running (say all jobs 
completed except 'D'), the 'Results' job is blocked (waiting for job 'D').  
This is correct.
However, once job 'D' got to the workspace cleanup post build step in its job 
configuration, the downstream job 'Results' would get triggered as if all 
upstream jobs were completed.  This is a problem.
Then when job 'D' actually finishes cleaning up the workspace, another build of 
job 'Results' is triggered.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira