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

P4 plugin should force sync when changing workspace root

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Linux
    • Similar Issues:

      Description

      When renaming a Hudson job, then perforce updates the client workspace root but does not perform a force sync.
      As a result, perforce attempts to sync to the new location but does not copy any files from P4 server because the
      "P4 have" table is telling perforce that the files already exist in the workspace.

      We find that the build will fail on every node after renaming a job.

      An easy way to fix this would be to run "P4 flush //...#0" after the workspace rename. This would tell perforce that the workspace is empty and the next regular sync would then sync all the files. Our assumption is that when Hudson renames the job that the workspace directory is not moved from the old location but is empty.

        Attachments

          Activity

            People

            • Assignee:
              rpetti Rob Petti
              Reporter:
              usammmy usammmy
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: