-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins 1.653
Project - Multi-configuration project with user defined Axis
In a matrix configuration project, with multiple user defined axis, when a p4 pull request is done to check if changes have been made to the workspace, it does not necessarily pull with the slave that the child was last built on.
For example:
Pull request is done for axis A on slave 1, triggers the build
Build for axis A is assigned and completed on slave 6
Pull request is done on slave 1, this will still trigger the build even if there have been no changes
Fix:
Change the behavior so for matrix jobs P4 polling happens on the slave that the child was last built on.
- is related to
-
JENKINS-37462 Polling breaks with multiple slaves with own workspace
- Closed