What is Continuous Delivery vs Continuous Deployment in Jenkins - Quick Revision & Key Takeaways

Recall & Review

beginner

What is Continuous Delivery?

Continuous Delivery is a software practice where code changes are automatically prepared for release to production. It ensures the code is always in a deployable state but requires a manual step to actually deploy.

beginner

What is Continuous Deployment?

Continuous Deployment is an extension of Continuous Delivery where every code change that passes automated tests is automatically deployed to production without manual intervention.

intermediate

How does Jenkins support Continuous Delivery?

Jenkins automates building, testing, and preparing code for release. It can trigger pipelines that package code and run tests, making sure the code is ready for deployment but waits for manual approval before releasing.

intermediate

How does Jenkins enable Continuous Deployment?

Jenkins pipelines can be configured to automatically deploy code to production after successful tests, removing manual steps and speeding up delivery to users.

beginner

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

The main difference is that Continuous Delivery requires a manual approval step before deployment, while Continuous Deployment automatically deploys every change that passes tests.

Which practice automatically deploys code changes to production after tests pass?

A Continuous Deployment

B Continuous Delivery

C Manual Deployment

D Version Control

Continuous Deployment automatically deploys code changes to production after passing tests.

In Continuous Delivery, what is required before code is released to production?

A No testing

B Automated deployment

C Manual approval

D Rollback

Continuous Delivery prepares code for release but requires manual approval before deployment.

How does Jenkins help in Continuous Delivery?

A By automating build and test pipelines

B By manually deploying code

C By writing code

D By managing servers

Jenkins automates building and testing code to prepare it for release.

What is a key benefit of Continuous Deployment?

A No testing required

B Faster delivery to users

C Slower releases

D More manual checks

Continuous Deployment speeds up delivery by automatically deploying changes.

Which statement is true about Continuous Delivery?

A It does not prepare code for release

B It skips testing

C It automatically deploys every change

D It always requires a manual deployment step

Continuous Delivery prepares code but needs manual deployment approval.

Explain the difference between Continuous Delivery and Continuous Deployment in simple terms.

Think about whether the deployment step is automatic or manual.

Describe how Jenkins can be used to implement Continuous Delivery and Continuous Deployment.

Focus on automation and manual steps in Jenkins pipelines.

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