Master-agent architecture in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins agent node in the pipeline.

Jenkins

pipeline {
  agent { label '[1]' }
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Amaster

Bagent

Cnode

Dslave

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'slave' which is deprecated terminology.

Using 'agent' which is a keyword, not a label.

Using 'node' which is a pipeline step, not a label.

The master label refers to the Jenkins master node where the pipeline runs if no specific agent is assigned.

2fill in blank

medium

Complete the code to run a stage on a specific Jenkins agent labeled 'linux'.

Jenkins

pipeline {
  agent none
  stages {
    stage('Test') {
      agent { label '[1]' }
      steps {
        echo 'Testing on Linux agent'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Awindows

Blinux

Cmac

Ddocker

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'windows' when the agent is Linux.

Using 'docker' which is not a label here.

Using 'mac' which is a different OS.

The label linux specifies the Jenkins agent node with that label to run the stage.

3fill in blank

hard

Fix the error in the Jenkins pipeline code to correctly allocate an agent node.

Jenkins

pipeline {
  agent [1]
  stages {
    stage('Deploy') {
      steps {
        echo 'Deploying application'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Alabel('any')

B'any'

Cany

D{ label: 'any' }

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around 'any' which causes syntax error.

Using a dictionary or function call which is invalid here.

The keyword any without quotes correctly tells Jenkins to run on any available agent.

4fill in blank

hard

Fill both blanks to define a Jenkins pipeline that runs on a specific agent and uses a shell step.

Jenkins

pipeline {
  agent { label '[1]' }
  stages {
    stage('Build') {
      steps {
        [2] 'echo Building on agent'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Alinux

Bsh

Cbat

Dwindows

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bat' which is for Windows agents.

Using 'windows' label with 'sh' step which causes errors.

The label linux selects the Linux agent, and sh runs a shell command on that agent.

5fill in blank

hard

Fill all three blanks to create a Jenkins pipeline that runs on an agent, checks out code, and runs a build command.

Jenkins

pipeline {
  agent { label '[1]' }
  stages {
    stage('Checkout') {
      steps {
        [2] scm
      }
    }
    stage('Build') {
      steps {
        [3] 'make build'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Alinux

Bcheckout

Csh

Dbat

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bat' on Linux agents causing errors.

Forgetting to use 'checkout' to get code.

Using wrong agent label.

The pipeline runs on a linux agent, uses checkout to get the source code, and runs the build command with sh.

Practice

1. What is the main role of the Jenkins master in the master-agent architecture?

easy

A. To run jobs on different machines

B. To control and schedule jobs

C. To store job logs only

D. To act as a backup server

Solution

1. Step 1: Understand the master role

   The Jenkins master is responsible for controlling and scheduling jobs, meaning it decides when and where jobs run.

2. Step 2: Differentiate from agent role

   Agents actually run the jobs on separate machines, not the master.

3. Final Answer:

   To control and schedule jobs -> Option B

4. Quick Check:

   Master controls jobs = B [OK]

Hint: Master schedules jobs; agents run them [OK]

Common Mistakes:

• Confusing master with agent role
• Thinking master runs jobs directly
• Assuming master only stores logs

2. Which of the following is the correct way to define an agent in a Jenkins pipeline script?

easy

A. run agent

B. master agent

C. agent any

D. node master

Solution

1. Step 1: Recall Jenkins pipeline syntax

   In Jenkins declarative pipeline, agent any means the job can run on any available agent.

2. Step 2: Check other options

   Options like master agent, run agent, and node master are not valid syntax for defining agents.

3. Final Answer:

   agent any -> Option C

4. Quick Check:

   Correct agent syntax = A [OK]

Hint: Use 'agent any' to run on any available agent [OK]

Common Mistakes:

• Using invalid keywords like 'master agent'
• Confusing 'node' with 'agent'
• Writing 'run agent' which is not valid

3. Given this Jenkins pipeline snippet, what will happen?

pipeline {
  agent { label 'linux' }
  stages {
    stage('Build') {
      steps {
        echo 'Building on Linux agent'
      }
    }
  }
}

medium

A. The job runs on any available agent

B. The job runs on the master node

C. The job fails due to syntax error

D. The job runs on an agent labeled 'linux'

Solution

1. Step 1: Analyze the agent label

   The pipeline specifies agent { label 'linux' }, so it will run on an agent with the label 'linux'.

2. Step 2: Understand job execution

   Since the label is specific, the job will not run on any agent or the master unless they have that label.

3. Final Answer:

   The job runs on an agent labeled 'linux' -> Option D

4. Quick Check:

   Agent label 'linux' = C [OK]

Hint: Agent label selects specific machine for job [OK]

Common Mistakes:

• Assuming 'agent any' runs here
• Thinking job runs on master by default
• Believing syntax causes failure

4. You configured an agent but Jenkins shows it as offline. What is the most likely cause?

medium

A. Agent machine is turned off or unreachable

B. Master node is overloaded

C. Pipeline syntax error in Jenkinsfile

D. Agent label does not match any job

Solution

1. Step 1: Understand agent offline status

   An agent shows offline if Jenkins cannot connect to it, often because the machine is off or network unreachable.

2. Step 2: Eliminate other causes

   Master overload or pipeline syntax errors do not cause agent offline status. Label mismatch prevents job assignment but does not make agent offline.

3. Final Answer:

   Agent machine is turned off or unreachable -> Option A

4. Quick Check:

   Offline agent = unreachable machine [OK]

Hint: Offline agent means machine unreachable or off [OK]

Common Mistakes:

• Blaming master overload for offline agent
• Confusing syntax errors with connectivity
• Thinking label mismatch causes offline

5. How can you improve Jenkins performance when running many jobs simultaneously using master-agent architecture?

hard

A. Add more agents to distribute the workload

B. Run all jobs on the master node to avoid delays

C. Disable agents to reduce network traffic

D. Use only one agent with high CPU

Solution

1. Step 1: Understand workload distribution

   Adding more agents allows Jenkins to run jobs in parallel on different machines, improving performance.

2. Step 2: Evaluate other options

   Running all jobs on master overloads it, disabling agents reduces capacity, and one agent limits parallelism.

3. Final Answer:

   Add more agents to distribute the workload -> Option A

4. Quick Check:

   More agents = better parallel job handling [OK]

Hint: More agents mean faster job execution [OK]

Common Mistakes:

• Overloading master with all jobs
• Disabling agents thinking it helps
• Relying on single powerful agent only