-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
P4 Plugin 1.11.4
When using previewOnly or FlushOnly for populate,
p4-plugin uses "p4 counter changes" and grabs the latest change number on the server. This may not reflect what changelist actually syncd on the client.
What p4-plugin does:
p4 counter change
p4 changes -m1 -ssubmitted //jenkins_test2_453/...@55287791
Instead it should use :
p4 changes -m1 -ssubmitted //jenkins_test2_453/...#have
To acquire the
[JENKINS-65982] P4 plugin reports incorrect changes on changes page when using populate:previewOnly
Description |
Original:
When using previewOnly or FlushOnly for populate,
p4-plugin uses "p4 counter changes" and grab the latest change number on the server. This may not reflect what the last change syncd to the client. What p4-plugin does: p4 counter change p4 changes -m1 -ssubmitted //jenkins_test2_453/...@55287791 Instead it should use : p4 changes -m1 -ssubmitted //jenkins_test2_453/...#have To acquire the |
New:
When using previewOnly or FlushOnly for populate,
p4-plugin uses "p4 counter changes" and grabs the latest change number on the server. This may not reflect what changelist actually syncd on the client. What p4-plugin does: p4 counter change p4 changes -m1 -ssubmitted //jenkins_test2_453/...@55287791 Instead it should use : p4 changes -m1 -ssubmitted //jenkins_test2_453/...#have To acquire the |
Assignee | New: Karl Wirth [ p4karl ] |