-
Bug
-
Resolution: Unresolved
-
Minor
-
None
A matrix build is supposed to sync on the same changeset for all versions of the builds running on all slaves.
When jobs are scheduled one after another and take some time, they sync on the latest commit, where they should sync to the last commit before the toplevel build started.
The previous version of the perforce plugin did this correct.
- relates to
-
JENKINS-65246 P4 Polling does not work correctly if changelist is specified during sync
-
- Closed
-
[JENKINS-71364] p4 plugin not syncing to same changeset in matrix build
Description |
New:
A matrix build is supposed to sync on the same changeset for all versions of the builds running on all slaves.
When jobs are scheduled one after another and take some time, they sync on the latest commit, where they should sync to the last commit before the toplevel build started. The previous version of the perforce plugin did this correct. |
Link |
New:
This issue relates to |
Comment | [ I think there is a variable "P4_CHANGELIST" set for each sub-build of the matrix builds, but it's not taken into account ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |