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

Perforce plug-in isn't showing changes in polling

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • p4-plugin
    • None
    • CentOS 4.8 (slave configuration)

      The front page of a given build says that it was started by an SCM change. Clicking through the link shows a log that simply says "Workspace not up to date" without any details of the files that have been changed.

      We're using "Disable Auto Sync" but I still expect the changed files would be included in the output from either the Polling Log or the Perforce Polling Log (it's not in either).

        1. screenshot-1.jpg
          screenshot-1.jpg
          43 kB
        2. screenshot-2.jpg
          screenshot-2.jpg
          42 kB
        3. screenshot-3.jpg
          screenshot-3.jpg
          37 kB
        4. screenshot-4.jpg
          screenshot-4.jpg
          36 kB

          [JENKINS-8529] Perforce plug-in isn't showing changes in polling

          Rob Petti added a comment -

          Good idea, it would help debugging polling issues quite a bit, since the output right now can be rather vague.

          Rob Petti added a comment - Good idea, it would help debugging polling issues quite a bit, since the output right now can be rather vague.

          halostatue added a comment -

          The first screen in the bug.

          halostatue added a comment - The first screen in the bug.

          halostatue added a comment -

          The 'standard' polling log (Perforce Polling Log doesn't always appear?)

          halostatue added a comment - The 'standard' polling log (Perforce Polling Log doesn't always appear?)

          halostatue added a comment -

          The Perforce Polling Log

          halostatue added a comment - The Perforce Polling Log

          halostatue added a comment -

          Output from our build script that shows the files that were updated.

          halostatue added a comment - Output from our build script that shows the files that were updated.

          halostatue added a comment -

          Added the screenshots that I couldn't figure out how to add when I first filed the bug.

          If I understood how the Perforce plug-in worked a bit better, I might be able to help work on this.

          halostatue added a comment - Added the screenshots that I couldn't figure out how to add when I first filed the bug. If I understood how the Perforce plug-in worked a bit better, I might be able to help work on this.

          Rob Petti added a comment -

          Ok, I think there's some confusion here. The polling log only shows the LAST poll that was done, regardless of what the result was. It's primarily used for debugging, nothing more.

          Since you are using "Disable Auto Sync", no perforce actions are performed in the build, including changeset retrieval. This behavior is also stated in the documentation for this option: "Disable Auto Sync: allows you to tell this plugin to not sync a workspace before the build begins. Changeset retrieval will also be disabled. Default behavior is to sync to the head revision."

          The option should definitely be renamed to avoid confusion (to "Disable Sync and Changelog" or something similar). The behavior you are looking for is covered by JENKINS-8260, and isn't yet implemented.

          I'll leave this bug open, though, since having the changes dumped to the polling log can still be useful for debugging.

          Rob Petti added a comment - Ok, I think there's some confusion here. The polling log only shows the LAST poll that was done, regardless of what the result was. It's primarily used for debugging, nothing more. Since you are using "Disable Auto Sync", no perforce actions are performed in the build, including changeset retrieval. This behavior is also stated in the documentation for this option: "Disable Auto Sync: allows you to tell this plugin to not sync a workspace before the build begins. Changeset retrieval will also be disabled. Default behavior is to sync to the head revision." The option should definitely be renamed to avoid confusion (to "Disable Sync and Changelog" or something similar). The behavior you are looking for is covered by JENKINS-8260 , and isn't yet implemented. I'll leave this bug open, though, since having the changes dumped to the polling log can still be useful for debugging.

            Unassigned Unassigned
            halostatue halostatue
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: