Failing fast principle in Jenkins - Mini Project: Build & Apply

Failing Fast Principle in Jenkins Pipeline

📖 Scenario: You are working as a DevOps engineer. Your team wants to create a Jenkins pipeline that quickly stops the build if a critical step fails. This helps save time and resources by not running unnecessary steps after a failure.

🎯 Goal: Build a Jenkins pipeline script that demonstrates the failing fast principle by stopping the pipeline immediately when a test step fails.

📋 What You'll Learn

Create a Jenkins pipeline with at least three stages: Build, Test, and Deploy.

Add a variable to control whether the test step should fail or pass.

Use the failing fast principle to stop the pipeline if the test step fails.

Print the pipeline status at the end.

💡 Why This Matters

🌍 Real World

Failing fast in CI/CD pipelines helps teams save time and resources by stopping builds early when critical errors occur.

💼 Career

Understanding and implementing failing fast is essential for DevOps engineers to create efficient and reliable automated pipelines.

1

Create the Jenkins pipeline with Build, Test, and Deploy stages

Write a Jenkins pipeline script with three stages named Build, Test, and Deploy. Each stage should have a simple echo command describing the stage.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
        stage('Test') {
            steps {
                // Your code here
            }
        }
        stage('Deploy') {
            steps {
                // Your code here
            }
        }
    }
}

Hint

Use stage('StageName') blocks and inside each, add steps { echo 'message' }.

2

Add a variable to control test success or failure

Add a boolean variable called shouldFailTest at the top of the pipeline script and set it to true. This variable will control if the test stage fails or passes.

Jenkins

def shouldFailTest = true

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Building the application...'
            }
        }
        stage('Test') {
            steps {
                echo 'Running tests...'
            }
        }
        stage('Deploy') {
            steps {
                echo 'Deploying the application...'
            }
        }
    }
}

# Your code here

Hint

Define def shouldFailTest = true before the pipeline block.

3

Implement failing fast logic in the Test stage

Modify the Test stage to check the shouldFailTest variable. If it is true, use error('Test failed') to stop the pipeline immediately. Otherwise, print 'Tests passed successfully.'.

Jenkins

def shouldFailTest = true

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Building the application...'
            }
        }
        stage('Test') {
            steps {
                script {
                    // Your code here
                }
            }
        }
        stage('Deploy') {
            steps {
                echo 'Deploying the application...'
            }
        }
    }
}

Hint

Use a script block inside the Test stage steps. Use if (shouldFailTest) { error('Test failed') } else echo.

4

Print pipeline status after all stages

Add a post block to the pipeline that prints 'Pipeline completed successfully.' if the pipeline succeeds, or 'Pipeline failed early due to test failure.' if it fails.

Jenkins

def shouldFailTest = true

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Building the application...'
            }
        }
        stage('Test') {
            steps {
                script {
                    if (shouldFailTest) {
                        error('Test failed')
                    } else {
                        echo 'Tests passed successfully.'
                    }
                }
            }
        }
        stage('Deploy') {
            steps {
                echo 'Deploying the application...'
            }
        }
    }
    post {
        // Your code here
    }
}

Hint

Add a post block with success and failure sections that print the required messages.

Practice

1. What does the failing fast principle mean in Jenkins pipelines?

easy

A. Run all steps twice to check for errors

B. Stop the pipeline immediately when an error occurs

C. Ignore errors and continue running all steps

D. Delay error handling until the end of the pipeline

Solution

1. Step 1: Understand the failing fast principle

   The principle means to stop work quickly when an error happens to save time and resources.

2. Step 2: Apply to Jenkins pipelines

   In Jenkins, this means the pipeline should stop immediately on error instead of continuing.

3. Final Answer:

   Stop the pipeline immediately when an error occurs -> Option B

4. Quick Check:

   Fail fast = stop immediately on error [OK]

Hint: Fail fast means stop immediately on error [OK]

Common Mistakes:

• Thinking pipeline should continue despite errors
• Confusing fail fast with retrying steps
• Assuming errors are handled at the end

2. Which Jenkins pipeline syntax correctly fails fast when a condition is not met?

easy

A. if (!condition) { echo('Fail fast') }

B. if (!condition) { sleep(10) }

C. if (!condition) { retry(3) }

D. if (!condition) { error('Fail fast') }

Solution

1. Step 1: Identify the Jenkins command to fail fast

   The error() step immediately stops the pipeline with a failure.

2. Step 2: Check the condition usage

   If the condition is false, calling error() triggers fail fast behavior.

3. Final Answer:

   if (!condition) { error('Fail fast') } -> Option D

4. Quick Check:

   Use error() to fail fast [OK]

Hint: Use error() to stop pipeline immediately [OK]

Common Mistakes:

• Using echo() which only prints message
• Using retry() which retries steps instead of failing
• Using sleep() which delays but does not fail

3. What will be the output of this Jenkins pipeline snippet?

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        script {
          if (false) {
            error('Fail fast triggered')
          }
          echo('Step completed')
        }
      }
    }
  }
}

medium

A. Pipeline prints 'Step completed' and succeeds

B. Pipeline fails with message 'Fail fast triggered'

C. Pipeline hangs indefinitely

D. Pipeline skips 'Step completed' but succeeds

Solution

1. Step 1: Analyze the condition in the script block

   The condition is false, so error() is not called.

2. Step 2: Check what happens next

   The pipeline executes echo('Step completed') and continues successfully.

3. Final Answer:

   Pipeline prints 'Step completed' and succeeds -> Option A

4. Quick Check:

   False condition skips error(), so pipeline succeeds [OK]

Hint: False condition means error() not called, pipeline continues [OK]

Common Mistakes:

• Assuming error() runs even if condition is false
• Thinking pipeline fails without error() call
• Confusing echo() with error()

4. Identify the error in this Jenkins pipeline snippet that tries to fail fast:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        script {
          if (buildStatus == 'FAILURE')
            error('Build failed')
        }
      }
    }
  }
}

medium

A. buildStatus variable is undefined

B. Incorrect use of error() function

C. Missing braces {} around if block

D. Pipeline syntax requires 'steps' outside 'script'

Solution

1. Step 1: Check variable definitions

   The buildStatus variable is not defined in the pipeline context.

2. Step 2: Verify standard Jenkins variables

   In Jenkins, use currentBuild.result or define buildStatus from previous steps to check status.

3. Final Answer:

   buildStatus variable is undefined -> Option A

4. Quick Check:

   Undefined variables cause runtime errors [OK]

Hint: Check for undefined variables in scripts [OK]

Common Mistakes:

• Assuming error() usage is wrong
• Ignoring undefined variables without context
• Misplacing steps and script blocks

5. You want your Jenkins pipeline to fail fast if any test stage fails, but continue running other stages if tests pass. Which approach best implements this?

hard

A. Use sleep() to delay failure until all tests complete

B. Use try-catch around test stages and call error() in catch

C. Use error() inside each test stage to stop pipeline on failure

D. Use catchError to mark test failures but continue pipeline

Solution

1. Step 1: Understand fail fast requirement

   Fail fast means stop pipeline immediately on test failure, so no further stages run.

2. Step 2: Evaluate options

   Using error() inside each test stage stops pipeline immediately on failure, matching fail fast.

3. Final Answer:

   Use error() inside each test stage to stop pipeline on failure -> Option C

4. Quick Check:

   Fail fast = error() stops pipeline immediately [OK]

Hint: Use error() in failing stages to stop pipeline fast [OK]

Common Mistakes:

• Using catchError which allows pipeline to continue
• Using try-catch which delays failure
• Using sleep() which only delays, not fails