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

Update P4 Documentation regarding Pin parameter

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.
      The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.

      As per comment below retitling as documentation task.

        Attachments

          Activity

          sumdumgai A C created issue -
          sumdumgai A C made changes -
          Field Original Value New Value
          Description Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.

          The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.
          Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.
          -
          The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.-

          As per comment below
          sumdumgai A C made changes -
          Description Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.
          -
          The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.-

          As per comment below
          Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.
          -
          The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.-

          As per comment below retitling as documentation task.
          sumdumgai A C made changes -
          Description Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.
          -
          The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.-

          As per comment below retitling as documentation task.
          Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.
          -The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.-

          As per comment below retitling as documentation task.
          sumdumgai A C made changes -
          Summary P4 workflow checkout should accept a changelist parameter Update P4 Documentation regarding Pin parameter
          p4paul Paul Allen made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 163136 ] JNJira + In-Review [ 208753 ]
          abayer Andrew Bayer made changes -
          Labels perforce workflow perforce pipeline workflow
          abayer Andrew Bayer made changes -
          Labels perforce pipeline workflow perforce pipeline

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            sumdumgai A C
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: