Failing fast principle in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Pipeline: What happens when a stage fails?

Consider this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'exit 1'
      }
    }
    stage('Test') {
      steps {
        echo 'Running tests'
      }
    }
  }
}

What will Jenkins do after the 'Build' stage fails?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'exit 1'
      }
    }
    stage('Test') {
      steps {
        echo 'Running tests'
      }
    }
  }
}

A Continue to the 'Test' stage despite the failure in 'Build'.

B Skip the 'Build' stage and run the 'Test' stage.

C Retry the 'Build' stage automatically before moving on.

D Stop the pipeline immediately and mark it as failed; the 'Test' stage will not run.

💡 Hint

Think about the default behavior of Jenkins pipelines when a shell command returns a non-zero exit code.

By default, Jenkins stops the pipeline immediately when a stage fails (non-zero exit code). This is the 'fail fast' principle to avoid wasting time on subsequent steps.

🧠 Conceptual

intermediate

Understanding the 'Failing Fast' Principle in Jenkins

Which statement best describes the 'Failing Fast' principle in Jenkins pipelines?

A The pipeline retries failed stages multiple times before stopping.

B The pipeline continues running all stages regardless of errors to collect maximum data.

C The pipeline stops execution immediately when an error occurs to save time and resources.

D The pipeline ignores errors and marks the build as successful.

💡 Hint

Consider why stopping early might be beneficial in automated builds.

'Failing Fast' means stopping the process as soon as a failure is detected to avoid wasting time and resources on subsequent steps that depend on the success of earlier ones.

🔀 Workflow

advanced

Configuring Jenkins to Fail Fast with Parallel Stages

You have a Jenkins pipeline with parallel stages. How can you configure it so that if any parallel stage fails, the entire pipeline stops immediately?

A Set <code>continueOnError true</code> in each parallel stage.

B Use the <code>failFast true</code> option inside the <code>parallel</code> block.

C Wrap each parallel stage in a <code>try-catch</code> block and ignore errors.

D Use <code>timeout</code> on each stage to stop after a fixed time.

💡 Hint

Look for a built-in option that controls failure behavior in parallel execution.

Jenkins supports a failFast true option inside the parallel block to stop all parallel branches as soon as one fails.

❓ Troubleshoot

advanced

Why does Jenkins continue after a failing shell command?

In a Jenkins pipeline, the shell command sh 'exit 1' is used, but the pipeline continues to the next stage instead of failing immediately. What is the most likely cause?

A The shell step is wrapped with <code>returnStatus: true</code>, so it returns the exit code instead of failing.

B The Jenkins agent is offline, so the command is skipped.

C The pipeline is configured with <code>failFast true</code>.

D The shell command syntax is incorrect, so it never runs.

💡 Hint

Check how Jenkins handles shell command exit codes when returnStatus is used.

Using returnStatus: true makes the shell step return the exit code as a number instead of failing the build, so the pipeline continues.

✅ Best Practice

expert

Implementing Fail Fast in a Complex Jenkins Pipeline

You have a Jenkins pipeline with multiple sequential and parallel stages. You want to ensure the pipeline fails fast on any error but also perform cleanup steps regardless of failure. Which Jenkins pipeline structure best achieves this?

A Use <code>try { ... } catch { ... } finally { cleanup }</code> blocks around stages, with <code>failFast true</code> in parallel blocks.

B Run all stages without error handling and add cleanup only at the end.

C Use <code>catchError</code> to ignore errors and run cleanup only if all stages succeed.

D Disable fail fast and rely on manual intervention to stop the pipeline.

💡 Hint

Think about combining fail fast behavior with guaranteed cleanup.

Using try-catch-finally allows the pipeline to fail fast on errors but still run cleanup steps in the finally block. The failFast true option stops parallel stages immediately on failure.