• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: p4-plugin
• Labels:

  None
• Environment:

  Jenkins 1.537
  Perforce plugin 1.3.26
  CentOS master
  Windows slave

[JENKINS-20901] Failed Perforce workspace wipe causes later builds to run with missing files

Nicolas Desjardins created issue - 2013-12-06 14:24

Nicolas Desjardins made changes - 2013-12-06 15:11

Description	Original: 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.	New: When the wipe workspace step fails for a Perforce client on a slave (due to or a connection failure or locked file for example), the next build on that slave does not sync all the files that were successfully deleted. It appears that the Perforce server believes that the workspace has 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.
Summary	Original: Failed Perforce sync causes later builds to run with missing files	New: Failed Perforce workspace wipe causes later builds to run with missing files

Rob Petti made changes - 2014-03-19 17:45

Assignee

Original: Rob Petti [ rpetti ]

R. Tyler Croy made changes - 2016-07-25 23:50

Workflow

Original: JNJira [ 152712 ]

New: JNJira + In-Review [ 178297 ]

Jenkins IRC Bot made changes - 2019-12-11 06:03

Component/s		New: p4-plugin [ 19224 ]
Component/s	Original: perforce-plugin [ 15506 ]