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

Jenkins multibranch pipeline keeps scheduling jobs to new nodes

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core

      We use a multi branch pipeline setup to build and test stuff when things are changed on a branch. We have multiple build nodes.

      I remember reading in documentation that the same job is supposed to be scheduled on the same node again if it is available. But that is not happening:

      It seems a new random node is chosen.

      This is rather unfortunate for us as we use incremental builds, i.e. it takes a very long time to build if we get a fresh checkout, but if we can reuse the previous checkout with all the intermediate files, the build time is much smaller.

          [JENKINS-51100] Jenkins multibranch pipeline keeps scheduling jobs to new nodes

          Esben Nielsen created issue -
          Mark Waite made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: git-plugin [ 15543 ]
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]
          jang hyemi (Inactive) made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          jang hyemi (Inactive) made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Joerg Schwaerzler made changes -
          Link New: This issue duplicates JENKINS-52529 [ JENKINS-52529 ]
          Jesse Glick made changes -
          Link New: This issue duplicates JENKINS-36547 [ JENKINS-36547 ]
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            esben Esben Nielsen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: