What is Continuous Delivery vs Continuous Deployment in Jenkins - Interactive Quiz & Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage for Continuous Delivery.

Jenkins

stage('Deploy to Staging') {
    steps {
        [1] 'deploy-to-staging'
    }
}

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

Ainput

BarchiveArtifacts

Ccheckout

Dsh

Attempts:

3 left

💡 Hint

Common Mistakes

Using input instead of sh for running commands.

The sh step runs shell commands, which is used here to deploy to staging in Continuous Delivery.

2fill in blank

medium

Complete the code to add a manual approval step in Continuous Delivery.

Jenkins

stage('Approval') {
    steps {
        [1] message: 'Approve deployment to production?'
    }
}

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

Aecho

Bsh

Cinput

Dtimeout

Attempts:

3 left

💡 Hint

Common Mistakes

Using sh instead of input for manual approval.

The input step pauses the pipeline and waits for manual approval, which is key in Continuous Delivery.

3fill in blank

hard

Fix the error in the Jenkins pipeline code to enable Continuous Deployment.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh 'make build'
            }
        }
        stage('Deploy') {
            steps {
                [1] 'deploy-to-production'
            }
        }
    }
}

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

Ainput

Bsh

Cecho

DarchiveArtifacts

Attempts:

3 left

💡 Hint

Common Mistakes

Using input which pauses for manual approval, not suitable for Continuous Deployment.

For Continuous Deployment, the deployment step should run automatically without manual input, so sh is correct to run deployment commands.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline snippet that shows the difference between Continuous Delivery and Continuous Deployment.

Jenkins

pipeline {
    agent any
    stages {
        stage('Deploy') {
            steps {
                [1] 'deploy-to-staging'
                [2] message: 'Approve production deployment?'
            }
        }
    }
}

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

Ash

Binput

Cecho

Dtimeout

Attempts:

3 left

💡 Hint

Common Mistakes

Using echo instead of sh for deployment commands.

Continuous Delivery deploys to staging automatically (sh) but waits for manual approval (input) before production.

5fill in blank

hard

Fill all three blanks to complete a Jenkins pipeline snippet that automates deployment fully for Continuous Deployment.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                [1] 'make build'
            }
        }
        stage('Test') {
            steps {
                [2] 'make test'
            }
        }
        stage('Deploy') {
            steps {
                [3] 'deploy-to-production'
            }
        }
    }
}

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

Ash

Binput

Cecho

DarchiveArtifacts

Attempts:

3 left

💡 Hint

Common Mistakes

Using input which pauses the pipeline, not suitable for Continuous Deployment.

In Continuous Deployment, all steps including build, test, and deploy run automatically using sh commands without manual approval.

Practice

1. What is the main difference between Continuous Delivery and Continuous Deployment?

easy

A. Continuous Delivery only builds code, Continuous Deployment only tests code.

B. Continuous Delivery deploys every change automatically, Continuous Deployment requires manual approval.

C. Continuous Delivery requires manual approval before production deployment, Continuous Deployment does not.

D. Continuous Delivery and Continuous Deployment are exactly the same.

Solution

1. Step 1: Understand Continuous Delivery

   Continuous Delivery automates preparing the software for release but waits for a manual step to deploy to production.

2. Step 2: Understand Continuous Deployment

   Continuous Deployment automates the entire process, including automatic deployment to production without manual approval.

3. Final Answer:

   Continuous Delivery requires manual approval before production deployment, Continuous Deployment does not. -> Option C

4. Quick Check:

   Manual approval = Continuous Delivery [OK]

Hint: Manual step means Continuous Delivery, no manual means Continuous Deployment [OK]

Common Mistakes:

• Confusing which process needs manual approval
• Thinking both deploy automatically
• Mixing build and deploy steps

2. Which Jenkins pipeline step is typically used to pause for manual approval in Continuous Delivery?

easy

A. input

B. deploy

C. build

D. test

Solution

1. Step 1: Identify Jenkins step for manual pause

   The input step in Jenkins pipeline pauses the pipeline and waits for user approval.

2. Step 2: Confirm other steps roles

   deploy runs deployment, build compiles code, test runs tests, none pause for approval.

3. Final Answer:

   input -> Option A

4. Quick Check:

   Manual approval step = input [OK]

Hint: Pause for approval uses 'input' step in Jenkins [OK]

Common Mistakes:

• Choosing deploy as manual step
• Confusing build or test with approval
• Not knowing Jenkins pipeline steps

3. Given this Jenkins pipeline snippet for Continuous Delivery:

stage('Deploy to Prod') {
  steps {
    input 'Approve deployment?'
    sh 'deploy.sh'
  }
}

What happens when this pipeline reaches the Deploy to Prod stage?

medium

A. The pipeline pauses and waits for manual approval before running deployment.

B. The pipeline fails with a syntax error.

C. The pipeline skips deployment and ends.

D. The deployment script runs immediately without pause.

Solution

1. Step 1: Analyze the input step in the stage

   The input 'Approve deployment?' pauses the pipeline and waits for a user to approve before continuing.

2. Step 2: Understand what happens after approval

   After approval, the shell script deploy.sh runs to deploy the application.

3. Final Answer:

   The pipeline pauses and waits for manual approval before running deployment. -> Option A

4. Quick Check:

   input step causes pause = The pipeline pauses and waits for manual approval before running deployment. [OK]

Hint: input step pauses pipeline until approval [OK]

Common Mistakes:

• Assuming deploy runs immediately
• Thinking pipeline skips deployment
• Confusing syntax error with input step

4. You have a Jenkins pipeline intended for Continuous Deployment but it includes this code:

stage('Deploy') {
  steps {
    input 'Approve deployment?'
    sh 'deploy.sh'
  }
}

What is the problem if you want full Continuous Deployment?

medium

A. The pipeline syntax is invalid and will fail.

B. The input step causes manual approval, breaking full automation.

C. The deploy.sh script is missing required parameters.

D. The stage name should be 'Continuous Deployment' instead of 'Deploy'.

Solution

1. Step 1: Identify manual approval in pipeline

   The input step pauses for manual approval, which is not allowed in full Continuous Deployment.

2. Step 2: Understand Continuous Deployment automation

   Continuous Deployment requires no manual steps; every change deploys automatically.

3. Final Answer:

   The input step causes manual approval, breaking full automation. -> Option B

4. Quick Check:

   Manual approval breaks Continuous Deployment [OK]

Hint: No manual steps allowed in Continuous Deployment [OK]

Common Mistakes:

• Thinking syntax error causes failure
• Assuming deploy.sh script is the problem
• Confusing stage name with functionality

5. You want to convert a Jenkins pipeline from Continuous Delivery to Continuous Deployment. Which change should you make?

hard

A. Rename the pipeline to 'Continuous Deployment' without changing steps.

B. Add more manual approval steps to ensure safety.

C. Change the build step to run tests only.

D. Remove the manual input approval step so deployment runs automatically.

Solution

1. Step 1: Identify manual approval in Continuous Delivery

   Continuous Delivery pipelines pause for manual approval using the input step.

2. Step 2: Remove manual approval for Continuous Deployment

   To achieve Continuous Deployment, remove the input step so deployment happens automatically after tests.

3. Final Answer:

   Remove the manual input approval step so deployment runs automatically. -> Option D

4. Quick Check:

   Remove manual steps for Continuous Deployment [OK]

Hint: Remove input step to automate deployment fully [OK]

Common Mistakes:

• Adding manual steps instead of removing
• Changing unrelated build steps
• Only renaming pipeline without changing logic