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.

Practice

1. What is the main purpose of using the parallel block in a Jenkins pipeline?

easy

A. To stop the pipeline if any test fails

B. To run multiple test groups at the same time to save time

C. To run tests one after another in a sequence

D. To deploy the application automatically after tests

Solution

1. Step 1: Understand the parallel block function

   The parallel block in Jenkins allows running multiple tasks simultaneously.

2. Step 2: Identify the benefit of parallel execution

   Running tests in parallel saves time by executing multiple test groups at once instead of sequentially.

3. Final Answer:

   To run multiple test groups at the same time to save time -> Option B

4. Quick Check:

   Parallel execution = run tests simultaneously [OK]

Hint: Parallel means running tasks at the same time [OK]

Common Mistakes:

• Thinking parallel runs tests one by one
• Confusing parallel with deployment steps
• Assuming parallel stops on first failure

2. Which of the following is the correct syntax to run two test stages in parallel in a Jenkins declarative pipeline?

easy

A. parallel {
stage('Test1') { steps { echo 'Run Test1' } }
stage('Test2') { steps { echo 'Run Test2' } }
}

B. parallel(
Test1: { stage('Test1') { steps { echo 'Run Test1' } } },
Test2: { stage('Test2') { steps { echo 'Run Test2' } } }
)

C. parallel(
Test1: { echo 'Run Test1' },
Test2: { echo 'Run Test2' }
)

D. parallel(
Test1: { steps { echo 'Run Test1' } },
Test2: { steps { echo 'Run Test2' } }
)

Solution

1. Step 1: Recall Jenkins parallel syntax

   In declarative pipelines, parallel takes a map of closures using scripted syntax with direct steps like echo.

2. Step 2: Check which option uses correct closure with direct steps

   parallel( Test1: { echo 'Run Test1' }, Test2: { echo 'Run Test2' } ) correctly uses parallel with keys and closures containing direct echo.

3. Final Answer:

   parallel( Test1: { echo 'Run Test1' }, Test2: { echo 'Run Test2' } ) -> Option C

4. Quick Check:

   parallel map with direct echo closures = parallel( Test1: { echo 'Run Test1' }, Test2: { echo 'Run Test2' } ) [OK]

Hint: parallel needs map keys with closures containing direct steps like echo [OK]

Common Mistakes:

• Using stage inside parallel directly (wrong in scripted)
• Adding steps block inside closures (declarative syntax mismatch)
• Using braces incorrectly for parallel syntax

3. Given the following Jenkins scripted pipeline snippet, what will be the output?

parallel(
  TestA: {
    echo 'Running Test A'
  },
  TestB: {
    echo 'Running Test B'
  }
)
echo 'All tests done'

medium

A. Running Test A\nRunning Test B\nAll tests done

B. Running Test A\nAll tests done\nRunning Test B

C. All tests done\nRunning Test A\nRunning Test B

D. Running Test B\nRunning Test A\nAll tests done

Solution

1. Step 1: Understand parallel execution output order

   Both TestA and TestB run at the same time, so their echo outputs appear before the next command.

2. Step 2: Identify the sequence of echo commands

   After both parallel tasks finish, the final echo 'All tests done' runs.

3. Final Answer:

   Running Test A\nRunning Test B\nAll tests done -> Option A

4. Quick Check:

   Parallel tests output first, then final echo [OK]

Hint: Parallel echoes appear before next sequential echo [OK]

Common Mistakes:

• Assuming output order is strictly sequential
• Thinking 'All tests done' prints before tests
• Confusing parallel output interleaving

4. You wrote this Jenkins pipeline snippet to run tests in parallel but it fails with a syntax error:

parallel(
  Test1: {
    stage('Test1') {
      steps {
        echo 'Running Test1'
      }
    }
  },
  Test2: {
    stage('Test2') {
      steps {
        echo 'Running Test2'
      }
    }
  }
)

What is the main cause of the error?

medium

A. Using parallel block outside a node block

B. Missing commas between parallel map entries

C. Incorrect indentation of the echo commands

D. Using stage and steps inside scripted pipeline closures

Solution

1. Step 1: Identify pipeline type and syntax rules

   In scripted pipelines, stage and steps blocks are not used inside closures passed to parallel.

2. Step 2: Recognize correct scripted pipeline parallel syntax

   Scripted pipelines use simple closures with commands like echo directly, without stage or steps.

3. Final Answer:

   Using stage and steps inside scripted pipeline closures -> Option D

4. Quick Check:

   Scripted parallel closures exclude stage/steps blocks [OK]

Hint: Scripted parallel closures don't use stage or steps blocks [OK]

Common Mistakes:

• Mixing declarative syntax inside scripted pipeline
• Forgetting commas between map entries (not the main error here)
• Assuming indentation causes syntax errors

5. You want to run three test suites in parallel in a Jenkins declarative pipeline and fail the entire build if any test fails. Which snippet correctly achieves this?

hard

A. stages {
stage('Parallel Tests') {
parallel {
Test1: { steps { sh 'run_test1.sh' } }
Test2: { steps { sh 'run_test2.sh' } }
Test3: { steps { sh 'run_test3.sh' } }
}
}
}

B. parallel {
stage('Test1') { steps { sh 'run_test1.sh' } }
stage('Test2') { steps { sh 'run_test2.sh' } }
stage('Test3') { steps { sh 'run_test3.sh' } }
}

C. stages {
parallel {
stage('Test1') { steps { sh 'run_test1.sh' } }
stage('Test2') { steps { sh 'run_test2.sh' } }
stage('Test3') { steps { sh 'run_test3.sh' } }
}
}

D. stage('Parallel Tests') {
parallel(
Test1: { sh 'run_test1.sh' },
Test2: { sh 'run_test2.sh' },
Test3: { sh 'run_test3.sh' }
)
}

Solution

1. Step 1: Recall declarative pipeline structure for parallel stages

   Declarative pipelines require a stages block containing stage blocks; parallel tests go inside a single stage with a parallel block.

2. Step 2: Identify correct syntax for parallel tests with failure propagation

   stages { stage('Parallel Tests') { parallel { Test1: { steps { sh 'run_test1.sh' } } Test2: { steps { sh 'run_test2.sh' } } Test3: { steps { sh 'run_test3.sh' } } } } } correctly uses stages block with a stage named 'Parallel Tests' containing a parallel block where each parallel branch is a closure with steps and sh commands. This is the proper declarative syntax and ensures the build fails if any test fails.

3. Final Answer:

   stages { stage('Parallel Tests') { parallel { Test1: { steps { sh 'run_test1.sh' } } Test2: { steps { sh 'run_test2.sh' } } Test3: { steps { sh 'run_test3.sh' } } } } } -> Option A

4. Quick Check:

   Declarative parallel inside a stage within stages block with steps closures [OK]

Hint: Use parallel inside a stage within stages block with steps closures [OK]

Common Mistakes:

• Placing parallel outside stages block
• Using parallel without wrapping in a stage
• Mixing scripted and declarative syntax