Parallel stages execution in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a parallel block in Jenkins pipeline.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build and Test') {
      steps {
        [1] {
          stage('Build') {
            steps {
              echo 'Building...'
            }
          }
          stage('Test') {
            steps {
              echo 'Testing...'
            }
          }
        }
      }
    }
  }
}

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

Aparallel

Bsequence

Cmatrix

Dscript

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'sequence' instead of 'parallel' causes stages to run one after another.

Using 'matrix' is for different combinations, not parallel execution.

The parallel block allows multiple stages to run at the same time in Jenkins pipeline.

2fill in blank

medium

Complete the code to name a parallel stage in Jenkins pipeline.

Jenkins

pipeline {
  agent any
  stages {
    stage('Parallel Work') {
      steps {
        parallel(
          [1]: {
            echo 'Running task A'
          },
          TaskB: {
            echo 'Running task B'
          }
        )
      }
    }
  }
}

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

A'TaskA'

BTaskA

C"TaskA"

DtaskA

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes causes syntax errors.

Using unquoted names is invalid in this context.

Parallel stage names must be strings, so they need quotes like 'TaskA'.

3fill in blank

hard

Fix the error in the parallel stages syntax.

Jenkins

pipeline {
  agent any
  stages {
    stage('Deploy') {
      steps {
        parallel {
          stage('Deploy to Dev') {
            steps {
              echo 'Deploying to Dev'
            }
          }
          stage('Deploy to Prod') {
            steps {
              echo 'Deploying to Prod'
            }
          }
        [1]
      }
    }
  }
}

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

A)

B}

C]

D;

Attempts:

3 left

💡 Hint

Common Mistakes

Using ')' or ']' causes syntax errors.

Missing the closing brace breaks the pipeline.

The parallel block uses curly braces { }, so it must be closed with }.

4fill in blank

hard

Fill both blanks to correctly define parallel stages with named tasks.

Jenkins

pipeline {
  agent any
  stages {
    stage('Parallel Tasks') {
      steps {
        parallel(
          [1]: {
            echo 'Task 1 running'
          },
          [2]: {
            echo 'Task 2 running'
          }
        )
      }
    }
  }
}

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

A'Task1'

B'Task2'

C'Build'

D'Test'

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted names causes errors.

Using same names for both tasks causes conflicts.

Parallel stages need unique string names as keys, like 'Task1' and 'Task2'.

5fill in blank

hard

Fill all three blanks to create a parallel block with three stages named Build, Test, and Deploy.

Jenkins

pipeline {
  agent any
  stages {
    stage('CI Pipeline') {
      steps {
        parallel(
          [1]: {
            echo 'Building...'
          },
          [2]: {
            echo 'Testing...'
          },
          [3]: {
            echo 'Deploying...'
          }
        )
      }
    }
  }
}

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

A'Build'

B'Test'

C'Deploy'

D'Release'

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted names causes syntax errors.

Using incorrect or duplicate names confuses the pipeline.

Each parallel stage must have a unique string name: 'Build', 'Test', and 'Deploy'.

Practice

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

easy

A. To run multiple stages at the same time to save time

B. To run stages one after another in a sequence

C. To pause the pipeline until manual approval

D. To restart the pipeline from the beginning

Solution

1. Step 1: Understand the role of parallel block

   The parallel block allows multiple tasks or stages to run simultaneously in Jenkins.

2. Step 2: Compare with other options

   Options A, B, and C describe restart, sequential execution, and manual pause, which are unrelated to parallel execution.

3. Final Answer:

   To run multiple stages at the same time to save time -> Option A

4. Quick Check:

   Parallel stages = run together [OK]

Hint: Parallel means tasks run at the same time, not one by one [OK]

Common Mistakes:

• Thinking parallel means sequential execution
• Confusing parallel with manual approval
• Assuming parallel restarts the pipeline

2. Which of the following is the correct syntax to define parallel stages inside a Jenkins pipeline?

easy

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

B. stage('Build') { parallel { stage('Test') { steps { echo 'Testing' } } } }

C. stage('Build') { steps { parallel { echo 'Building' } } }

D. parallel([ "Build": { steps { echo 'Building' } }, "Test": { steps { echo 'Testing' } } ])

Solution

1. Step 1: Recall correct parallel syntax

   The parallel block should use a map of branches, each containing steps.

2. Step 2: Analyze options

   parallel([ "Build": { steps { echo 'Building' } }, "Test": { steps { echo 'Testing' } } ]) correctly defines parallel branches. Options B, C, and D misuse the placement of parallel or stages.

3. Final Answer:

   parallel([ "Build": { steps { echo 'Building' } }, "Test": { steps { echo 'Testing' } } ]) -> Option D

4. Quick Check:

   parallel wraps stages directly [OK]

Hint: Parallel wraps multiple stages side by side, not inside one stage [OK]

Common Mistakes:

• Putting parallel inside steps block
• Nesting stages inside other stages incorrectly
• Using parallel with single stage only

3. Given this Jenkins pipeline snippet, what will be the output order of the echo statements?

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

medium

A. Running A\nRunning B

B. Running B\nRunning A

C. Running A and Running B in any order or simultaneously

D. Syntax error due to nested stages inside parallel

Solution

1. Step 1: Understand parallel execution output

   Stages inside parallel run at the same time, so their output order is not guaranteed.

2. Step 2: Check syntax validity

   The syntax is valid for parallel branches inside a stage's steps block, so no syntax error occurs.

3. Final Answer:

   Running A and Running B in any order or simultaneously -> Option C

4. Quick Check:

   Parallel stages output order is unpredictable [OK]

Hint: Parallel means output order can vary, no fixed sequence [OK]

Common Mistakes:

• Assuming output order is always A then B
• Thinking nested stages cause syntax error here
• Expecting sequential output in parallel block

4. You wrote this Jenkins pipeline snippet but it fails with a syntax error:

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        parallel {
          stage('Unit') {
            steps { echo 'Unit tests' }
          }
          stage('Integration') {
            steps { echo 'Integration tests' }
          }
        }
      }
    }
  }
}

What is the error and how to fix it?

medium

A. stage names inside parallel must be unique; rename stages

B. parallel block cannot contain nested stage blocks directly; use map syntax with branches

C. parallel block requires agent declaration inside each stage

D. steps block cannot contain echo commands

Solution

1. Step 1: Identify parallel block syntax rules

   The parallel directive expects a map of branch names to closures containing steps, not loose stage blocks inside {}.

2. Step 2: Fix the pipeline structure

   Change to parallel( "Unit": { echo 'Unit tests' }, "Integration": { echo 'Integration tests' } ) to fix the syntax error.

3. Final Answer:

   parallel block cannot contain nested stage blocks directly; use map syntax with branches -> Option B

4. Quick Check:

   parallel uses branch map syntax [OK]

Hint: parallel must be outside steps block, directly under stage [OK]

Common Mistakes:

• Placing parallel inside steps block
• Ignoring pipeline syntax hierarchy
• Assuming echo commands cause error

5. You want to run three tasks in parallel: 'Build', 'Test', and 'Deploy'. The 'Deploy' stage should only run if both 'Build' and 'Test' succeed. How do you structure the Jenkins pipeline to achieve this?

hard

A. Use parallel for 'Build' and 'Test' stages, then a separate 'Deploy' stage after parallel block

B. Put all three stages inside a single parallel block

C. Run 'Deploy' inside parallel block with 'Build' and 'Test' but add a condition to skip if others fail

D. Run 'Deploy' before 'Build' and 'Test' in parallel block

Solution

1. Step 1: Understand dependency requirements

   'Deploy' must wait for 'Build' and 'Test' to finish successfully, so it cannot run in parallel with them.

2. Step 2: Structure pipeline accordingly

   Run 'Build' and 'Test' inside a parallel block, then add a separate 'Deploy' stage after that block to run only if previous succeed.

3. Final Answer:

   Use parallel for 'Build' and 'Test' stages, then a separate 'Deploy' stage after parallel block -> Option A

4. Quick Check:

   Dependent stage runs after parallel block [OK]

Hint: Run dependent stages after parallel block, not inside it [OK]

Common Mistakes:

• Putting dependent stage inside parallel block
• Running deploy before build and test
• Trying to conditionally skip stages inside parallel