Parallel stages execution in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of parallel stages in Jenkins pipeline

Consider this Jenkins pipeline snippet using parallel to run two stages simultaneously:

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

What will be the order of the output lines in the Jenkins console?

Jenkins

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

A Running A and Running B lines can appear in any order or interleaved

B Running B\nRunning A

C No output because parallel stages do not print

D Running A\nRunning B

💡 Hint

Think about how parallel execution affects output order.

Parallel stages run simultaneously, so their output lines can appear in any order or interleaved in the Jenkins console.

❓ Configuration

intermediate

Correct syntax for parallel stages in Jenkins scripted pipeline

Which of the following Jenkins scripted pipeline snippets correctly defines two parallel stages named 'Test' and 'Build'?

Jenkins

parallel(
  Test: {
    echo 'Testing'
  },
  Build: {
    echo 'Building'
  }
)

A

parallel(
  Test: {
    echo 'Testing'
  },
  Build: {
    echo 'Building'
  }
)

B

parallel([
  Test: {
    echo 'Testing'
  },
  Build: {
    echo 'Building'
  }
])

C

parallel {
  stage('Test') {
    echo 'Testing'
  }
  stage('Build') {
    echo 'Building'
  }
}

D

parallel(
  stage('Test') {
    echo 'Testing'
  },
  stage('Build') {
    echo 'Building'
  }
)

💡 Hint

Remember scripted pipeline uses parallel with a map of closures.

In scripted pipeline, parallel takes a map where keys are stage names and values are closures with steps. Option A matches this syntax exactly.

❓ Troubleshoot

advanced

Why does a parallel stage fail to run all branches?

A Jenkins declarative pipeline uses parallel to run three branches: 'Lint', 'Test', and 'Deploy'. However, only 'Lint' and 'Test' run, and 'Deploy' is skipped without error. What is the most likely cause?

A Parallel stages cannot have more than two branches

B The 'Deploy' stage is inside a <code>when</code> condition that evaluates to false

C The Jenkins agent does not support parallel execution

D The 'Deploy' stage has a syntax error causing it to be ignored

💡 Hint

Check conditions that control stage execution.

If a stage has a when condition that evaluates to false, Jenkins skips it silently even in parallel blocks.

🔀 Workflow

advanced

Order of execution in nested parallel stages

Given this Jenkins declarative pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Main') {
      parallel {
        stage('Branch1') {
          steps { echo 'Branch1' }
        }
        stage('Branch2') {
          parallel {
            stage('Sub1') {
              steps { echo 'Sub1' }
            }
            stage('Sub2') {
              steps { echo 'Sub2' }
            }
          }
        }
      }
    }
  }
}

Which statement about the output order is true?

A 'Sub1' and 'Sub2' run sequentially after 'Branch1' completes

B 'Branch1' always prints before 'Sub1' and 'Sub2'

C Only 'Branch1' runs because nested parallel is not supported

D Output lines 'Branch1', 'Sub1', and 'Sub2' can appear in any order or interleaved

💡 Hint

Think about how nested parallel blocks behave.

All parallel branches, including nested ones, run concurrently, so their output can appear in any order or interleaved.

✅ Best Practice

expert

Best practice to handle failures in parallel stages

In a Jenkins pipeline with multiple parallel stages, what is the best practice to ensure that if one stage fails, the others continue running and the pipeline reports the failure at the end?

A Use <code>failFast true</code> in the parallel block to stop all on first failure

B Do not use parallel stages if failures are expected

C Wrap each parallel stage steps in <code>try-catch</code> to catch errors and record failures manually

D Use <code>parallel</code> with <code>failFast false</code> and rely on Jenkins default behavior

💡 Hint

Consider how to isolate failures and still report them.

Wrapping each parallel stage in try-catch allows stages to continue running despite failures and lets you record and report failures explicitly at the end.