Major 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.
[JENKINS-28301] Update P4 Documentation regarding Pin parameter
A C
created issue -
A C
made changes -
| Description |
Original:
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. |
New:
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 |
A C
made changes -
| Description |
Original:
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 |
New:
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. |
A C
made changes -
| Description |
Original:
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. |
New:
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. |
A C
made changes -
| Summary | Original: P4 workflow checkout should accept a changelist parameter | New: Update P4 Documentation regarding Pin parameter |
Paul Allen
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 163136 ] | New: JNJira + In-Review [ 208753 ] |
| Labels | Original: perforce workflow | New: perforce pipeline workflow |
| Labels | Original: perforce pipeline workflow | New: perforce pipeline |