-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
RHEL5
Hudson 1.372
Perforce Plugin 1.1.10
Master/Slave (4 nodes, all RHEL5)
I have several Maven2 jobs that run on a schedule and on occasion, randomly, one or more of those jobs will fail because the workspace is mysteriously empty. I will have to go into the Perforce configuration and force the workspace to be synced and run the build again and it'll be fine for a day or two. The Perforce plugin flag to clear the workspace is NOT set, and the flag to force a sync is also not automatically enabled (when I check after a failed build) - so it seems that maybe it's not the plugin clearing the workspace. I also can't tell when it's cleared, whether it's before or after a build, but for whatever reason the build thinks everything is kosher then fails because it can't find the POM. This began happening some time ago after upgrading 1.372, but never happened on the prior version (1.342 I think).
- is related to
-
JENKINS-10615 Workspaces seem to be removed prematurely on concurrent jobs
-
- Resolved
-
I'll put in my 2 cents. There's a hook on the "Wipe out workspace" function that calls out to the SCM to notify it that it's being deleted. When that happens, the perforce plugin will force sync on the next build, which will pull all the code from the SCM again. Since this is not happening, I'm guessing that something else is deleting the workspace. Another plugin, or a bad build script could be at fault, and perhaps even a stray crontab or obnoxious co-worker...