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

Workspace changes does not trigger a full sync

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None

      If a job's Jenkins workspace changes then a full sync is not done.

      Easy to replicate.

      Create a job with a custom workspace e.g: /workspace/test/
      Do a sync and build
      Check in a single file
      Change custom workspace to /workspace/test2
      Run job.
      New local workspace has only the single change.

      On a jenkins workspace change a full sync needs to happen to make sure the p4 have lists and local files are actually correct

          [JENKINS-25332] Workspace changes does not trigger a full sync

          Morne Joubert created issue -
          Morne Joubert made changes -
          Priority Original: Critical [ 2 ] New: Major [ 3 ]
          Rob Petti made changes -
          Assignee Original: Rob Petti [ rpetti ]
          Oleg Nenashev made changes -
          Link New: This issue is related to JENKINS-23467 [ JENKINS-23467 ]
          Oleg Nenashev made changes -
          Link Original: This issue is related to JENKINS-23467 [ JENKINS-23467 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 159251 ] New: JNJira + In-Review [ 179934 ]
          Jenkins IRC Bot made changes -
          Component/s New: p4-plugin [ 19224 ]
          Component/s Original: perforce-plugin [ 15506 ]

            Unassigned Unassigned
            mornejoubert Morne Joubert
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: