Jenkins multibranch pipeline keeps scheduling jobs to new nodes

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Critical
    • Component/s: core
    • Environment:

      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.

            Assignee:
            Unassigned
            Reporter:
            Esben Nielsen
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: