|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I want to add that the real problem might be that job B is trying to get the archive from job A, but A completed and replaced the last successful build. So Job B downloaded a part from the former archive and would continue with the new one. That results in a broken archive on the slave node for job B.
Maybe this is not a clone workspace bug a Jenkins core bug? If jobs, which are dependent on another job, are running the dependent job might not finish but wait until no other job accesses its resources?