Failing fast principle in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to stop the Jenkins pipeline immediately on failure.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        script {
          sh 'make build' || [1]
        }
      }
    }
  }
}

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

Aerror('Build failed')

Becho 'Build failed'

Creturn

Dsleep 10

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo only prints a message but does not stop the pipeline.

Using return does not fail the pipeline in this context.

Sleeping delays but does not stop the pipeline.

Using error('Build failed') stops the pipeline immediately when the build fails, following the failing fast principle.

2fill in blank

medium

Complete the code to fail fast if tests do not pass.

Jenkins

stage('Test') {
  steps {
    script {
      def status = sh(script: 'make test', returnStatus: true)
      if (status != 0) [1]
    }
  }
}

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

Aerror('Tests failed')

Bsleep 5

Creturn

Decho 'Tests failed'

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo only logs a message but does not stop the pipeline.

Using return does not fail the pipeline here.

Sleeping delays but does not fail the pipeline.

The error('Tests failed') step immediately fails the pipeline if tests fail, implementing fail fast.

3fill in blank

hard

Fix the error in the Jenkins pipeline to fail fast on deployment failure.

Jenkins

stage('Deploy') {
  steps {
    script {
      def result = sh(script: 'deploy.sh', returnStatus: true)
      if (result == 0) {
        echo 'Deployment succeeded'
      } else [1]
    }
  }
}

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

Aecho 'Deployment failed'

Berror('Deployment failed')

Creturn

Dsleep 10

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo only logs but does not stop the pipeline.

Using return does not fail the pipeline here.

Sleeping delays but does not stop the pipeline.

Using error('Deployment failed') causes the pipeline to stop immediately on deployment failure, following fail fast.

4fill in blank

hard

Fill both blanks to fail fast if linting or security scan fails.

Jenkins

stage('Quality Checks') {
  steps {
    script {
      def lintStatus = sh(script: 'lint.sh', returnStatus: true)
      if (lintStatus != 0) [1]
      def scanStatus = sh(script: 'security_scan.sh', returnStatus: true)
      if (scanStatus != 0) [2]
    }
  }
}

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

Aerror('Linting failed')

Becho 'Linting failed'

Cerror('Security scan failed')

Dsleep 5

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo only logs messages but does not stop the pipeline.

Using sleep delays but does not fail the pipeline.

Both error('Linting failed') and error('Security scan failed') stop the pipeline immediately on failure, implementing fail fast.

5fill in blank

hard

Fill all three blanks to fail fast if any critical step fails in this Jenkins pipeline.

Jenkins

pipeline {
  agent any
  stages {
    stage('Critical Steps') {
      steps {
        script {
          def buildStatus = sh(script: 'build.sh', returnStatus: true)
          if (buildStatus != 0) [1]
          def testStatus = sh(script: 'test.sh', returnStatus: true)
          if (testStatus != 0) [2]
          def deployStatus = sh(script: 'deploy.sh', returnStatus: true)
          if (deployStatus != 0) [3]
        }
      }
    }
  }
}

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

Aerror('Build failed')

Berror('Tests failed')

Cerror('Deployment failed')

Decho 'Step failed'

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo only logs messages but does not stop the pipeline.

Not handling all failure cases causes the pipeline to continue despite errors.

Each error() call stops the pipeline immediately on failure of build, test, or deploy steps, following the fail fast principle.

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