Matrix builds for multi-platform in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a Jenkins matrix build with two platforms

Given the following Jenkins pipeline snippet, what will be the output printed for the PLATFORM variable during the build?

Jenkins

pipeline {
  agent none
  stages {
    stage('Build') {
      matrix {
        axes {
          axis {
            name 'PLATFORM'
            values 'linux', 'windows'
          }
        }
        stages {
          stage('Print Platform') {
            agent any
            steps {
              echo "Building on ${PLATFORM}"
            }
          }
        }
      }
    }
  }
}

A Building on linux\nBuilding on windows

B Building on linux

C Building on windows

D Building on linux\nBuilding on linux

💡 Hint

Think about how matrix axes create parallel builds for each value.

The matrix axis 'PLATFORM' has two values: 'linux' and 'windows'. Jenkins runs the inner stages once for each value, so the echo step runs twice, printing both platforms.

❓ Configuration

intermediate

Correct matrix axis syntax for multi-platform builds

Which of the following Jenkins pipeline matrix axis configurations correctly defines a multi-platform build for 'linux' and 'mac'?

A

axis {
  name: 'PLATFORM'
  values: ['linux', 'mac']
}

B

axis {
  name = 'PLATFORM'
  values = ['linux', 'mac']
}

C

axis {
  name 'PLATFORM'
  values 'linux', 'mac'
}

D

axis {
  PLATFORM = ['linux', 'mac']
}

💡 Hint

Jenkins pipeline uses Groovy syntax without equals or colons in this context.

The correct syntax uses 'name' and 'values' as keywords without assignment operators. Options A, B, and D use invalid Groovy syntax for this block.

❓ Troubleshoot

advanced

Why does the Jenkins matrix build fail with 'No agent specified' error?

Consider this Jenkins pipeline snippet: pipeline { agent none stages { stage('Build') { matrix { axes { axis { name 'OS' values 'linux', 'windows' } } stages { stage('Compile') { steps { echo "Compiling on ${OS}" } } } } } } } Why does this pipeline fail with a 'No agent specified' error?

A Because the 'echo' step is not allowed inside matrix stages.

B Because the matrix axis name 'OS' is invalid and causes the build to fail.

C Because the 'matrix' block requires an 'agent any' declaration at the top level.

D Because the 'Compile' stage inside matrix does not specify an agent, and the parent agent is 'none'.

💡 Hint

Remember that each stage needs an agent unless inherited from parent.

The pipeline sets 'agent none' globally, so each stage must specify an agent. The 'Compile' stage inside the matrix does not specify any agent, causing the error.

🔀 Workflow

advanced

Matrix build with environment variables per platform

You want to run a Jenkins matrix build for platforms 'linux' and 'windows'. For 'windows', you need to set an environment variable WIN_PATH to C:\\Build. Which pipeline snippet correctly sets this environment variable only for the windows build?

A

matrix {
  axes {
    axis {
      name 'PLATFORM'
      values 'linux', 'windows'
    }
  }
  stages {
    stage('Build') {
      steps {
        script {
          if (PLATFORM == 'windows') {
            env.WIN_PATH = 'C:\\Build'
          }
          echo "Platform: ${PLATFORM}, Path: ${env.WIN_PATH}"
        }
      }
    }
  }
}

B

matrix {
  axes {
    axis {
      name 'PLATFORM'
      values 'linux', 'windows'
    }
  }
  stages {
    stage('Build') {
      environment {
        WIN_PATH = 'C:\\Build'
      }
      steps {
        echo "Platform: ${PLATFORM}, Path: ${WIN_PATH}"
      }
    }
  }
}

C

matrix {
  axes {
    axis {
      name 'PLATFORM'
      values 'linux', 'windows'
    }
  }
  environment {
    WIN_PATH = 'C:\\Build'
  }
  stages {
    stage('Build') {
      steps {
        echo "Platform: ${PLATFORM}, Path: ${WIN_PATH}"
      }
    }
  }
}

D

matrix {
  axes {
    axis {
      name 'PLATFORM'
      values 'linux', 'windows'
    }
  }
  stages {
    stage('Build') {
      steps {
        echo "Platform: ${PLATFORM}, Path: ${WIN_PATH}"
      }
    }
  }
  environment {
    WIN_PATH = 'C:\\Build'
  }
}

💡 Hint

Environment variables can be set dynamically inside a script block.

Only option A sets the environment variable conditionally inside a script block, so WIN_PATH is defined only for windows builds. Other options set WIN_PATH unconditionally or incorrectly.

✅ Best Practice

expert

Optimizing Jenkins matrix builds for resource usage

You have a Jenkins matrix build with 3 axes: OS (linux, windows), JDK (8, 11), and DB (mysql, postgres). This creates 12 parallel builds. Your Jenkins server has limited executors. What is the best way to optimize resource usage without losing coverage?

A Use the 'failFast true' option in the matrix to stop all builds if one fails, saving resources.

B Use the 'maxParallel' option to limit the number of concurrent builds running at once.

C Reduce the number of axes values by removing less important combinations to lower total builds.

D Run all builds sequentially by setting 'parallel false' to avoid overloading executors.

💡 Hint

Think about controlling concurrency rather than removing coverage or running sequentially.

The 'maxParallel' option limits how many matrix combinations run at the same time, balancing resource use and coverage. 'failFast' stops builds on failure but doesn't reduce concurrency. Removing axes reduces coverage. Running sequentially wastes time.