![]() |
|
|
|
|
Change By:
|
Nicolas Desjardins
(06/Dec/13 3:11 PM)
|
|
Summary:
|
Failed Perforce
sync
workspace wipe
causes later builds to run with missing files
|
|
Description:
|
When
the wipe workspace step fails for
a Perforce
sync fails
client
on a slave (due to
running out of disk space
or a connection failure
or locked file
for example), the next build on that slave does not sync all the files
missed during the original sync
that were successfully deleted
.
It appears that the Perforce server believes that the workspace has
synced
all
the
files
synced
, but the slave does not have them. Obviously, without all the files, that next build fails.
When this happens, I have to force a clean sync on the slave to correct the problem.
|
|
|
|
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.
