Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34037

P4 polling always triggers if matrix axis is built on a different slave

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • p4-plugin
    • 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.

            Unassigned Unassigned
            tim_fredrickson Tim Fredrickson
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: