![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Rob Petti
|
|
Components:
|
perforce |
|
Created:
|
06/Dec/13 2:24 PM
|
|
Description:
|
When a Perforce sync fails on a slave (due to running out of disk space or a connection failure for example), the next build on that slave does not sync all the files missed during the original sync.
It appears that the Perforce server believes that the workspace has synced all files, 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.
|
|
Environment:
|
Jenkins 1.537
Perforce plugin 1.3.26
CentOS master
Windows slave
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Nicolas Desjardins
|
|
|
|
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/groups/opt_out.
