-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 2.263.3
P4-Plugin 1.11.2
If a changelist is specified in scm: checkout, p4 polling does not work. The result is the specified changelist is used in the range:
P4: Polling with range: 53910841,53910841
p4 changes -m20 //clientname_/...@53910841,53910841
This result, is polling will not detect any subsequent changes.
If changelist is not specified during scm: checkout,
P4: Polling with range: 53910841,now
p4 changes -m20 //clientname_/...@53910841,now
P4 plugin should always use "now" for the higher end of the range, regardless if a changelist was specified or not.
- relates to
-
JENKINS-71143 Pipeline code is not synced to pinned label in multibranch pipelines
-
- Open
-
-
JENKINS-71364 p4 plugin not syncing to same changeset in matrix build
-
- In Progress
-
-
JENKINS-63879 Using pin to sync to changelist causes polling to no longer detect changes beyond pinned CL
-
- Closed
-
[JENKINS-65246] P4 Polling does not work correctly if changelist is specified during sync
Assignee | New: Paul Allen [ p4paul ] |
Assignee | Original: Paul Allen [ p4paul ] | New: Karl Wirth [ p4karl ] |
Labels | New: P4_SUPPORT |
Comment |
[ It seems this is potentially a dup of [ |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Labels | Original: P4_SUPPORT | New: P4_A P4_VERIFY |
Link |
New:
This issue relates to |
Link | New: This issue relates to JENKINS-71364 [ JENKINS-71364 ] |
Link | New: This issue relates to JENKINS-71143 [ JENKINS-71143 ] |
Comment | [ Hi [~heiko_nardmann] many thanks for the offer to help test this. I have emailed you (using the email id mentioned on our salesforce account) the hpi file you can try on your setup. Of course since this is a beta release, would be prudent to try it on a not-so-risky scenario (of course this fix shouldn't cause anything drastic anyway). Thanks! ] |