Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-20901

Failed Perforce workspace wipe causes later builds to run with missing files

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None
    • Jenkins 1.537
      Perforce plugin 1.3.26
      CentOS master
      Windows slave

      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.

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

          There are no comments yet on this issue.

            Unassigned Unassigned
            ndesjardins Nicolas Desjardins
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: