Remove executors on Jenkins master

Remove executors on Jenkins master

The DriveTrain Jenkins enabled on the Salt Master node enables you to run any job on any Jenkins slave or master. Though, running a job on Jenkins master can lead to job failures since Jenkins master is not intended to be a job executor.

Starting from the MCP 2019.2.4 maintenance update, MCP disables executors on Jenkins master by default to prevent failures of the jobs that run on the Salt Master node. For the MCP versions earlier than 2019.2.4, Mirantis recommends setting zero executors on Jenkins master to disable jobs scheduling on this agent node as described below.

Note

If Jenkins is disabled on the Salt Master node (for details, refer to MCP Deployment Guide: Deploy CI/CD), you can skip the steps below or simply update your cluster configuration without applying the Salt states.

To set zero executors on Jenkins master on the Salt Master node:

  1. Log in to the Salt Master node.

  2. In ./classes/cluster/<cluster_name>/infra/config/jenkins.yml, add the following pillar data:

    parameters:
      _param:
        jenkins:
          client:
            ...
            node:
              master:
                num_executors: 0
               ...
    
  3. Refresh pillars:

    salt -C 'I@salt:master' saltutil.refresh_pillar
    
  4. Apply the changes:

    salt -C 'I@salt:master' state.apply jenkins.client