I have a Matrix Job which runs on multiple agents.

      These agents are provided by Swarm Client, and are marked as "exclusive" such that they should only run jobs which match the agent label.

      However, the matrix job's initial "flyweight" light weight master job automatically selects this node as the master, and results in the build failing because this particular agent does not have the Git utilities installed, so it cannot run the flyweight task.

      I had assumed that "exclusive" really would be "exclusive" and would prevent flyweight tasks from selecting this machine.

          [JENKINS-40729] flyweight task executing on exclusive agent

          Jacob Keller added a comment -

          For reference, commit 55bf88329027 ("If every node is restricted to tied jobs only, Matrix build jobs can never start.", 2013-06-18) of the Jenkins CORE changed this behavior. Unfortunately, this means that exclusive nodes no longer ignore flyweight jobs if the master node cannot itself host the jobs.

          I think this needs to be refined somewhat, and possibly simply be considered an error.

          Jacob Keller added a comment - For reference, commit 55bf88329027 ("If every node is restricted to tied jobs only, Matrix build jobs can never start.", 2013-06-18) of the Jenkins CORE changed this behavior. Unfortunately, this means that exclusive nodes no longer ignore flyweight jobs if the master node cannot itself host the jobs. I think this needs to be refined somewhat, and possibly simply be considered an error.

          Oleg Nenashev added a comment -

          KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Oleg Nenashev added a comment - KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Basil Crow added a comment -

          jenkinsci/jenkins#3983 should mitigate this issue quite a bit. Can you please try upgrading to Jenkins 2.222.x LTS or later and see if the problem still occurs?

          Basil Crow added a comment - jenkinsci/jenkins#3983 should mitigate this issue quite a bit. Can you please try upgrading to Jenkins 2.222.x LTS or later and see if the problem still occurs?

            Unassigned Unassigned
            jekeller Jacob Keller
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: