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

Jenkins multibranch pipeline keeps scheduling jobs to new nodes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
    • Environment:
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            markewaite Mark Waite added a comment -

            The selection of agents for job execution is part of core, not part of the git plugin.

            The git plugin can help long checkout times by using the suggestions in "Git Tips and Tricks". Reference repositories and narrow refspecs can both provide significant savings for clone time.

            Show
            markewaite Mark Waite added a comment - The selection of agents for job execution is part of core, not part of the git plugin. The git plugin can help long checkout times by using the suggestions in " Git Tips and Tricks ". Reference repositories and narrow refspecs can both provide significant savings for clone time.
            Hide
            esben Esben Nielsen added a comment -

            Found the documentation:

            Scheduling Strategy

            "Jenkins tries to build a project on the same computer that it was previously built."

            Might be a problem with for multibranch pipeline, where each branch isn't counted as it's own project in the above?

             

            Show
            esben Esben Nielsen added a comment - Found the documentation: Scheduling Strategy "Jenkins tries to build a project on the same computer that it was previously built." Might be a problem with for multibranch pipeline, where each branch isn't counted as it's own project in the above?  
            Hide
            macdrega Joerg Schwaerzler added a comment -

            Same happens for plain pipeline jobs. This is related to pipeline jobs in general.

            Show
            macdrega Joerg Schwaerzler added a comment - Same happens for plain pipeline jobs. This is related to pipeline jobs in general.
            Hide
            macdrega Joerg Schwaerzler added a comment -

            Created a more general issue; already opened PR there.

            Show
            macdrega Joerg Schwaerzler added a comment - Created a more general issue; already opened PR there.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: