|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

We experience the same problem, also on Windows. While the original bug report mentioned one executor running multiple jobs, we have multiple executors but only one job. We trigger builds when a change gets uploaded to Gerrit. When enough changes get uploaded at the right time a build will start on an executor that is still running the post-build actions of a previous build. This is really annoying because builds fail regularly because of this bug.
We have "Execute concurrent builds if necessary" enabled for the job in question. We use git with the "clean workspace" option enabled which deletes the files the previous build still requires in its post-actions.
The scenario is this: