Build, test, deploy stages concept in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline with a build stage.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        [1] 'echo Building the project'
      }
    }
  }
}

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

Acommand

Brun

Csh

Dexecute

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' or 'execute' which are not Jenkins pipeline steps.

Forgetting to use a step to run shell commands.

The sh step runs shell commands in Jenkins pipelines. Here, it runs the echo command in the build stage.

2fill in blank

medium

Complete the code to add a test stage that runs tests using a shell command.

Jenkins

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

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

Aexecute

Bcommand

Crun

Dsh

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent steps like 'execute' or 'run'.

Not using a step to run shell commands.

The sh step is used to run shell commands like test scripts in Jenkins pipelines.

3fill in blank

hard

Fix the error in the deploy stage by completing the code to run a shell command.

Jenkins

pipeline {
  agent any
  stages {
    stage('Deploy') {
      steps {
        [1] 'echo Deploying application'
      }
    }
  }
}

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

Ash

Bexecute

Crun

Dcommand

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid steps like 'execute' or 'run'.

Omitting the step to run shell commands.

The sh step is required to run shell commands in Jenkins pipelines, including deployment commands.

4fill in blank

hard

Fill both blanks to create a pipeline with build and test stages that run shell commands.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        [1] 'echo Building'
      }
    }
    stage('Test') {
      steps {
        [2] 'echo Testing'
      }
    }
  }
}

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

Ash

Brun

Cexecute

Dcommand

Attempts:

3 left

💡 Hint

Common Mistakes

Using different or invalid steps for build and test stages.

Forgetting to use a step to run shell commands.

Both build and test stages use the sh step to run shell commands.

5fill in blank

hard

Fill all three blanks to create a full pipeline with build, test, and deploy stages running shell commands.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        [1] 'echo Build started'
      }
    }
    stage('Test') {
      steps {
        [2] 'echo Test started'
      }
    }
    stage('Deploy') {
      steps {
        [3] 'echo Deploy started'
      }
    }
  }
}

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

Ash

Brun

Cexecute

Dcommand

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing different steps for different stages.

Using invalid steps that cause errors.

All stages use the sh step to run shell commands in Jenkins pipelines.

Practice

1. What is the main purpose of splitting a Jenkins pipeline into build, test, and deploy stages?

easy

A. To organize the process into clear steps and catch errors early

B. To run all commands at the same time for speed

C. To skip testing and deploy directly

D. To only build the code without testing or deploying

Solution

1. Step 1: Understand the purpose of stages

   Stages separate the pipeline into logical parts: building, testing, and deploying.

2. Step 2: Recognize benefits of stages

   This separation helps find errors early and keeps the process organized.

3. Final Answer:

   To organize the process into clear steps and catch errors early -> Option A

4. Quick Check:

   Stages = clear steps + early error detection [OK]

Hint: Stages split work to catch errors early and stay organized [OK]

Common Mistakes:

• Thinking stages run in parallel by default
• Skipping test stage to save time
• Confusing build with deploy

2. Which of the following is the correct syntax to define a build stage in a Jenkins declarative pipeline?

easy

A. stage('build') { steps { sh 'make build' } }

B. build { stage('steps') { sh 'make build' } }

C. steps { stage('build') { sh 'make build' } }

D. pipeline { build { sh 'make build' } }

Solution

1. Step 1: Recall Jenkins declarative syntax

   A stage is defined as stage('name') { steps { ... } }.

2. Step 2: Match syntax with options

   stage('build') { steps { sh 'make build' } } correctly uses stage('build') { steps { sh 'make build' } }.

3. Final Answer:

   stage('build') { steps { sh 'make build' } } -> Option A

4. Quick Check:

   Stage syntax = stage('name') + steps block [OK]

Hint: Stage syntax: stage('name') { steps { ... } } [OK]

Common Mistakes:

• Placing steps outside stage block
• Using build as a block instead of stage
• Missing steps keyword

3. Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('build') {
      steps {
        echo 'Building...'
      }
    }
    stage('test') {
      steps {
        error 'Test failed!'
      }
    }
    stage('deploy') {
      steps {
        echo 'Deploying...'
      }
    }
  }
}

What will be the output when this pipeline runs?

medium

A. Pipeline skips build and test, runs deploy only

B. All stages run successfully including deploy

C. Build stage runs, then test stage fails and stops pipeline; deploy does not run

D. Pipeline runs build and deploy but skips test

Solution

1. Step 1: Analyze build stage

   The build stage prints 'Building...' successfully.

2. Step 2: Analyze test stage

   The test stage runs error 'Test failed!' which stops the pipeline with failure.

3. Step 3: Analyze deploy stage

   Because test failed, deploy stage does not run.

4. Final Answer:

   Build stage runs, then test stage fails and stops pipeline; deploy does not run -> Option C

5. Quick Check:

   Failure in test stops pipeline before deploy [OK]

Hint: Error in test stage stops pipeline before deploy [OK]

Common Mistakes:

• Assuming deploy runs despite test failure
• Thinking error only logs message without stopping
• Ignoring pipeline stop on error

4. You wrote this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('build') {
      steps {
        sh 'make build'
      }
    }
    stage('test') {
      sh 'make test'
    }
    stage('deploy') {
      steps {
        sh 'make deploy'
      }
    }
  }
}

Why does this pipeline fail to run correctly?

medium

A. The build stage uses sh instead of bat

B. The test stage is missing the steps block

C. The deploy stage should be outside stages

D. The agent keyword is misplaced

Solution

1. Step 1: Check syntax of each stage

   Build and deploy stages have steps { ... } blocks, but test stage does not.

2. Step 2: Understand Jenkins syntax rules

   Each stage must have a steps block to run commands; missing it causes failure.

3. Final Answer:

   The test stage is missing the steps block -> Option B

4. Quick Check:

   Missing steps block in stage = syntax error [OK]

Hint: Every stage needs a steps block for commands [OK]

Common Mistakes:

• Forgetting steps block inside a stage
• Mixing shell commands syntax
• Misplacing agent keyword

5. You want to create a Jenkins pipeline that builds your app, runs tests, and deploys only if tests pass. Which pipeline structure below correctly implements this with proper stages and error handling?

hard

A. pipeline { agent any stages { stage('build') { steps { sh 'build.sh' } } stage('test') { steps { sh 'test.sh' } } stage('deploy') { steps { sh 'deploy.sh' } } } }

B. pipeline { agent any stages { stage('build') { steps { sh 'build.sh' } } stage('test') { steps { sh 'test.sh' } } stage('deploy') { steps { sh 'deploy.sh' } } } post { failure { echo 'Tests failed, skipping deploy' } } }

C. pipeline { agent any stages { stage('build') { steps { sh 'build.sh' } } stage('test') { steps { sh 'test.sh' } } stage('deploy') { steps { sh 'deploy.sh' } } } post { always { echo 'Deploying regardless of test result' } } }

D. pipeline { agent any stages { stage('build') { steps { sh 'build.sh' } } stage('test') { steps { sh 'test.sh' } } stage('deploy') { steps { sh 'deploy.sh' } } } post { success { echo 'Deployment complete' } } }

Solution

1. Step 1: Understand pipeline flow

   Build runs first, then test, then deploy only if test passes (pipeline success).

2. Step 2: Analyze post blocks

   pipeline { agent any stages { stage('build') { steps { sh 'build.sh' } } stage('test') { steps { sh 'test.sh' } } stage('deploy') { steps { sh 'deploy.sh' } } } post { success { echo 'Deployment complete' } } } uses post { success { ... } } to confirm deployment success message, matching requirement.

3. Step 3: Check other options

   pipeline { agent any stages { stage('build') { steps { sh 'build.sh' } } stage('test') { steps { sh 'test.sh' } } stage('deploy') { steps { sh 'deploy.sh' } } } } lacks error handling; B prints message on failure but does not prevent deploy; C deploys always.

4. Final Answer:

   Option D correctly runs deploy only on success and confirms deployment -> Option D

5. Quick Check:

   Deploy runs only if tests pass = post success block [OK]

Hint: Use post success block to run deploy only if tests pass [OK]

Common Mistakes:

• Deploy running even if tests fail
• Missing post blocks for error handling
• Confusing post always with success