Why pipeline quality matters in Jenkins - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage named 'Build'.

Jenkins

stage('[1]') {
    steps {
        echo 'Building the project'
    }
}

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

AClean

BTest

CDeploy

DBuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong stage name like 'Test' or 'Deploy' here.

The stage name should be 'Build' to represent the build step in the pipeline.

2fill in blank

medium

Complete the code to add a post-build action that always runs.

Jenkins

post {
    [1] {
        echo 'Cleaning up workspace'
    }
}

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

Afailure

Bsuccess

Calways

Dunstable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'success' or 'failure' which run conditionally.

The 'always' block runs regardless of the build result, ensuring cleanup happens every time.

3fill in blank

hard

Fix the error in the pipeline syntax to correctly define an agent.

Jenkins

pipeline {
    agent [1]
    stages {
        stage('Test') {
            steps {
                echo 'Running tests'
            }
        }
    }
}

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

Aany

B'any'

Cnode

D'node'

Attempts:

3 left

💡 Hint

Common Mistakes

Putting quotes around 'any' causing syntax errors.

The agent should be specified as any without quotes to indicate any available agent.

4fill in blank

hard

Fill both blanks to create a stage that runs only when the branch is 'main'.

Jenkins

stage('Deploy') {
    when {
        [1] '[2]'
    }
    steps {
        echo 'Deploying to production'
    }
}

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

Abranch

Benvironment

Cmain

Dfeature

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'environment' or wrong branch names like 'feature'.

The when condition uses branch 'main' to run the stage only on the main branch.

5fill in blank

hard

Fill all three blanks to define a pipeline with an agent, environment variable, and a stage.

Jenkins

pipeline {
    agent [1]
    environment {
        APP_ENV = '[2]'
    }
    stages {
        stage('[3]') {
            steps {
                echo "Environment is $APP_ENV"
            }
        }
    }
}

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

Aany

Bproduction

CDeploy

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around agent, wrong environment values, or incorrect stage names.

The pipeline uses agent any to run on any agent, sets APP_ENV to 'production', and defines a 'Deploy' stage.

Practice

1.

Why is maintaining high quality in Jenkins pipelines important?

easy

A. It reduces errors and saves time during software delivery.

B. It makes the pipeline run slower to catch more bugs.

C. It allows skipping tests to speed up deployment.

D. It only benefits the developers, not the whole team.

Solution

1. Step 1: Understand pipeline quality impact

   High quality pipelines automate tests and builds, reducing manual errors and saving time.

2. Step 2: Consider team collaboration benefits

   Good pipelines help the whole team by providing reliable feedback and smoother workflows.

3. Final Answer:

   It reduces errors and saves time during software delivery. -> Option A

4. Quick Check:

   Pipeline quality = fewer errors and saved time [OK]

Hint: Good pipelines save time and reduce errors [OK]

Common Mistakes:

• Thinking pipeline quality slows down delivery
• Believing skipping tests improves quality
• Assuming only developers benefit

2.

Which of the following is the correct syntax to define a simple Jenkins pipeline stage?

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        ?
      }
    }
  }
}

easy

A. execute 'make build'

B. run 'make build'

C. sh 'make build'

D. command 'make build'

Solution

1. Step 1: Identify Jenkins pipeline step syntax

   Jenkins uses sh 'command' to run shell commands in pipeline steps.

2. Step 2: Match correct command format

   Only sh 'make build' matches the correct syntax for running a shell command.

3. Final Answer:

   sh 'make build' -> Option C

4. Quick Check:

   Shell commands use sh 'command' syntax [OK]

Hint: Use sh 'command' to run shell commands in Jenkins [OK]

Common Mistakes:

• Using run or execute instead of sh
• Omitting quotes around the command
• Using unsupported keywords like command

3.

Given this Jenkins pipeline snippet, what will be the output if the test stage fails?

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
    stage('Test') {
      steps {
        error 'Tests failed!'
      }
    }
    stage('Deploy') {
      steps {
        echo 'Deploying...'
      }
    }
  }
}

medium

A. Pipeline stops before Build stage.

B. Build stage runs, Test stage fails, Deploy stage is skipped.

C. All stages run regardless of test failure.

D. Deploy stage runs even if Test fails.

Solution

1. Step 1: Understand error step behavior

   The error step causes the pipeline to fail immediately at that stage.

2. Step 2: Trace pipeline execution flow

   Build stage runs successfully, Test stage fails with error, so Deploy stage is skipped.

3. Final Answer:

   Build stage runs, Test stage fails, Deploy stage is skipped. -> Option B

4. Quick Check:

   Pipeline stops on error step failure [OK]

Hint: error step stops pipeline immediately [OK]

Common Mistakes:

• Assuming all stages run despite failure
• Thinking pipeline stops before Build
• Believing Deploy runs after Test failure

4.

Identify the error in this Jenkins pipeline snippet that causes the pipeline to fail unexpectedly:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
    stage('Test') {
      steps {
        sh 'exit 1'
      }
    }
    stage('Deploy') {
      steps {
        echo 'Deploying...'
      }
    }
  }
}

medium

A. Deploy stage syntax is invalid.

B. The echo command in Build stage is incorrect.

C. Missing agent declaration causes failure.

D. The sh 'exit 1' command causes the Test stage to fail.

Solution

1. Step 1: Analyze the Test stage command

   The command sh 'exit 1' returns a failure exit code, causing the stage to fail.

2. Step 2: Understand pipeline failure impact

   When a stage fails, the pipeline stops and subsequent stages like Deploy do not run.

3. Final Answer:

   The sh 'exit 1' command causes the Test stage to fail. -> Option D

4. Quick Check:

   Exit code 1 in shell step causes failure [OK]

Hint: Exit code 1 in shell step fails pipeline [OK]

Common Mistakes:

• Thinking echo command causes failure
• Ignoring agent declaration presence
• Assuming Deploy stage syntax is wrong

5.

You want to improve your Jenkins pipeline to catch errors early and avoid deploying broken code. Which combination of pipeline quality practices should you apply?

hard

A. Add automated tests in the pipeline and fail fast on errors.

B. Skip tests to speed up deployment and manually check later.

C. Deploy first, then run tests to save time.

D. Run tests only after deployment to production.

Solution

1. Step 1: Identify best practices for pipeline quality

   Automated tests help catch errors early, and failing fast prevents broken code from progressing.

2. Step 2: Evaluate options for deployment safety

   Skipping tests or deploying before testing risks deploying broken code, which is unsafe.

3. Final Answer:

   Add automated tests in the pipeline and fail fast on errors. -> Option A

4. Quick Check:

   Automated tests + fail fast = better pipeline quality [OK]

Hint: Fail fast with tests to catch errors early [OK]

Common Mistakes:

• Skipping tests to save time
• Deploying before testing
• Testing only after production deployment