Parallel test execution in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Pipeline Parallel Stage Output

Given the following Jenkins pipeline snippet, what will be the output order of the stages when executed?

Jenkins

pipeline {
  agent any
  stages {
    stage('Parallel Tests') {
      parallel {
        stage('Test A') {
          steps {
            echo 'Running Test A'
          }
        }
        stage('Test B') {
          steps {
            echo 'Running Test B'
          }
        }
      }
    }
  }
}

A Only Test A message appears; Test B is skipped.

B Test A message appears first, then Test B message after Test A finishes.

C Test A and Test B messages appear simultaneously in the console output.

D Test B message appears first, then Test A message after Test B finishes.

💡 Hint

Think about how Jenkins runs parallel stages in the pipeline.

In Jenkins, stages defined inside a parallel block run at the same time. Their output messages can appear interleaved or nearly simultaneously in the console.

❓ Configuration

intermediate

Configuring Parallel Test Execution in Jenkinsfile

Which Jenkinsfile snippet correctly configures two test suites to run in parallel with separate agents?

A

parallel {
  test1: {
    agent any
    steps { echo 'Running test1' }
  }
  test2: {
    agent any
    steps { echo 'Running test2' }
  }
}

B

parallel(
  test1: {
    steps { echo 'Running test1' }
  },
  test2: {
    steps { echo 'Running test2' }
  }
)

C

parallel(
  stage('test1') {
    steps { echo 'Running test1' }
  },
  stage('test2') {
    steps { echo 'Running test2' }
  }
)

D

parallel {
  stage('test1') {
    agent any
    steps { echo 'Running test1' }
  }
  stage('test2') {
    agent any
    steps { echo 'Running test2' }
  }
}

💡 Hint

Remember the correct syntax for parallel stages inside a Jenkins pipeline.

In declarative Jenkins pipelines, parallel stages are defined inside a parallel block with nested stage blocks, each can have its own agent and steps.

❓ Troubleshoot

advanced

Troubleshooting Parallel Stage Failure in Jenkins

You have a Jenkins pipeline with parallel test stages. One stage fails but the others continue running. Which configuration causes this behavior?

Jenkins

pipeline {
  agent any
  stages {
    stage('Parallel Tests') {
      parallel {
        stage('Test 1') {
          steps {
            error 'Test 1 failed'
          }
        }
        stage('Test 2') {
          steps {
            echo 'Test 2 running'
          }
        }
      }
    }
  }
}

A The pipeline is configured to fail fast, so all stages stop immediately on any failure.

B The pipeline uses default behavior where parallel stages run independently; failure in one does not stop others.

C The pipeline uses a try-catch block around parallel stages to ignore failures.

D The pipeline uses a 'failFast true' option inside parallel to stop all on failure.

💡 Hint

Consider Jenkins default behavior for parallel stage failures.

By default, Jenkins runs parallel stages independently. If one fails, others continue unless failFast true is set.

🔀 Workflow

advanced

Optimizing Parallel Test Execution Workflow

You want to run 10 test suites in parallel but limit Jenkins to run only 3 at a time to avoid resource overload. Which approach achieves this?

A Use <code>throttleConcurrentBuilds</code> plugin to limit parallel executions to 3.

B Use a <code>parallel</code> block with all 10 tests inside; Jenkins will automatically limit concurrency to 3.

C Split the 10 tests into groups of 3 and run each group sequentially with <code>parallel</code> inside each group.

D Use <code>failFast true</code> in the <code>parallel</code> block to limit concurrency.

💡 Hint

Think about Jenkins plugins that control concurrency.

The throttleConcurrentBuilds plugin allows limiting the number of concurrent builds or parallel executions to control resource usage.

✅ Best Practice

expert

Best Practice for Sharing Data Between Parallel Stages

In a Jenkins pipeline with parallel test stages, you want to share a file generated by one stage with another stage running in parallel. What is the best practice to achieve this?

A Use Jenkins stash and unstash steps to share files between parallel stages.

B Write the file to the workspace; all parallel stages share the same workspace by default.

C Use environment variables to pass file contents between stages.

D Write the file to a temporary directory on the agent; parallel stages can access it directly.

💡 Hint

Consider how Jenkins isolates parallel stages and how files can be shared safely.

Parallel stages may run on different agents or separate workspaces. Using stash and unstash steps is the recommended way to share files safely between stages.