Parallel test execution in Jenkins - Time & Space Complexity

Time Complexity: Parallel test execution

O(1)

Understanding Time Complexity

When running tests in Jenkins, we often want to run many tests quickly. Parallel test execution helps by running tests at the same time.

We want to understand how the total time changes as we add more tests and run them in parallel.

Scenario Under Consideration

Analyze the time complexity of the following Jenkins pipeline snippet that runs tests in parallel.

pipeline {
  agent any
  stages {
    stage('Run Tests') {
      steps {
        parallel (
          "Test 1": {
            sh 'run_test_1.sh'
          },
          "Test 2": {
            sh 'run_test_2.sh'
          },
          "Test 3": {
            sh 'run_test_3.sh'
          }
        )
      }
    }
  }
}

This code runs three test stages at the same time instead of one after another.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Running each test script (Test 1, Test 2, Test 3).
• How many times: Each test runs once, but all run simultaneously.

How Execution Grows With Input

Imagine we have n tests to run.

Input Size (n)	Approx. Operations
10	Runs 10 tests in parallel, total time close to longest single test.
100	Runs 100 tests in parallel, total time close to longest single test.
1000	Runs 1000 tests in parallel, total time close to longest single test.

Pattern observation: Total time does not grow much with more tests because they run at the same time.

Final Time Complexity

Time Complexity: O(1)

This means the total time to run all tests stays about the same no matter how many tests run in parallel.

Common Mistake

[X] Wrong: "Running more tests in parallel always takes more time because there are more tests."

[OK] Correct: When tests run at the same time, total time depends mostly on the longest test, not the number of tests.

Interview Connect

Understanding how parallel execution affects time helps you explain how to speed up processes in real projects. It shows you can think about work done at the same time versus one after another.

Self-Check

"What if the tests cannot run fully in parallel because of limited resources? How would the time complexity change?"

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