Blue-green deployment pattern in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of the blue-green deployment pattern?

To reduce downtime and risk by running two identical production environments (blue and green) and switching traffic between them during deployment.

beginner

In blue-green deployment, what happens to the inactive environment during deployment?

The inactive environment is updated with the new version of the application while the active environment continues serving users.

intermediate

How does Jenkins help implement blue-green deployments?

Jenkins automates the deployment process by running pipelines that update the inactive environment, run tests, and switch traffic when ready.

intermediate

What is a key benefit of blue-green deployment compared to traditional deployment?

It allows instant rollback by switching back to the previous environment if issues occur, minimizing downtime and user impact.

beginner

Which component typically manages the traffic switching in a blue-green deployment?

A load balancer or router directs user traffic to either the blue or green environment based on the active deployment.

What does the 'green' environment represent in blue-green deployment?

A The inactive environment being updated

B The currently active production environment

C A testing environment unrelated to production

D The backup database

In blue-green deployment, the green environment is the inactive one where the new version is deployed before switching traffic.

How does blue-green deployment reduce downtime?

A By deploying updates directly on the active environment

B By running two environments and switching traffic instantly

C By stopping all user traffic during deployment

D By deploying only small code changes

Blue-green deployment runs two identical environments and switches user traffic instantly to the updated one, avoiding downtime.

Which Jenkins feature is most useful for blue-green deployments?

A User authentication

B Static code analysis

C Pipeline automation

D Artifact repository

Jenkins pipelines automate the deployment steps needed for blue-green deployments, such as updating environments and switching traffic.

What is the main risk mitigated by blue-green deployment?

A Security vulnerabilities

B Code merge conflicts

C Long deployment times

D Deployment failures causing downtime

Blue-green deployment reduces the risk of downtime caused by deployment failures by allowing quick rollback.

What role does a load balancer play in blue-green deployment?

A It switches user traffic between environments

B It runs automated tests

C It stores deployment logs

D It builds the application code

The load balancer directs user traffic to either the blue or green environment, enabling smooth switching during deployment.

Explain how blue-green deployment works and why it is useful.

Think about having two copies of your app and switching between them.

Describe how Jenkins pipelines can automate a blue-green deployment.

Consider how Jenkins can run commands and control deployment flow.

Practice

1. What is the main goal of the blue-green deployment pattern in Jenkins?

easy

A. To deploy only on weekends

B. To run tests faster by using multiple agents

C. To backup data before deployment

D. To avoid downtime by switching between two identical environments

Solution

1. Step 1: Understand blue-green deployment concept

   This pattern uses two identical environments called blue and green to deploy new versions without downtime.

2. Step 2: Identify the main goal in Jenkins context

   Jenkins automates switching traffic between these environments to keep the service available during updates.

3. Final Answer:

   To avoid downtime by switching between two identical environments -> Option D

4. Quick Check:

   Blue-green deployment = avoid downtime [OK]

Hint: Blue-green means two environments for zero downtime [OK]

Common Mistakes:

• Confusing blue-green with backup strategies
• Thinking it speeds up tests
• Assuming deployment timing is the main goal

2. Which Jenkins pipeline step correctly switches traffic from the blue environment to the green environment?

easy

A. sh 'kubectl patch service myapp -p "{\"spec\":{\"selector\":{\"env\":\"green\"}}}'

B. sh 'kubectl apply -f green-service.yaml'

C. sh 'kubectl scale deployment blue --replicas=0'

D. sh 'kubectl delete pod blue-pod-1'

Solution

1. Step 1: Understand traffic switching in Kubernetes

   Switching traffic means updating the service selector to point to the new environment pods.

2. Step 2: Identify the correct kubectl command

   The patch command changes the service selector to 'green', redirecting traffic from blue to green.

3. Final Answer:

   sh 'kubectl patch service myapp -p "{\"spec\":{\"selector\":{\"env\":\"green\"}}}' -> Option A

4. Quick Check:

   Patch service selector = switch traffic [OK]

Hint: Patch service selector to switch environments [OK]

Common Mistakes:

• Scaling down blue does not switch traffic immediately
• Applying green service config alone doesn't switch traffic
• Deleting pods causes downtime

3. Given this Jenkins pipeline snippet, what will be the output if the green environment is healthy?

stage('Deploy Green') {
  steps {
    sh 'kubectl apply -f green-deployment.yaml'
    sh 'kubectl rollout status deployment/green'
  }}
stage('Switch Traffic') {
  steps {
    sh 'kubectl patch service myapp -p "{\"spec\":{\"selector\":{\"env\":\"green\"}}}'
  }}

medium

A. Traffic remains on blue environment

B. Deployment fails because green environment is missing

C. Deployment applies and traffic switches to green with no errors

D. Rollout status command causes syntax error

Solution

1. Step 1: Analyze deployment commands

   The green deployment is applied and rollout status waits for it to be ready.

2. Step 2: Analyze traffic switch command

   The patch command updates the service selector to green, switching traffic successfully.

3. Final Answer:

   Deployment applies and traffic switches to green with no errors -> Option C

4. Quick Check:

   Healthy green + patch service = success [OK]

Hint: Healthy rollout then patch service switches traffic [OK]

Common Mistakes:

• Assuming rollout status causes errors
• Thinking traffic stays on blue after patch
• Confusing deployment apply with service patch

4. You have a Jenkins pipeline that deploys to green, but users report downtime after switching traffic. What is the most likely cause?

medium

A. The Jenkinsfile syntax is incorrect

B. The green deployment rollout was not completed before switching traffic

C. The blue environment was deleted before switching

D. The service selector was not patched to green

Solution

1. Step 1: Understand downtime cause in blue-green

   Downtime happens if traffic switches before the new environment is ready.

2. Step 2: Identify pipeline mistake

   If rollout status is skipped or incomplete, green pods may not be ready, causing downtime.

3. Final Answer:

   The green deployment rollout was not completed before switching traffic -> Option B

4. Quick Check:

   Incomplete rollout before switch = downtime [OK]

Hint: Wait for rollout status before switching traffic [OK]

Common Mistakes:

• Deleting blue early does not cause downtime if green is ready
• Syntax errors cause pipeline failure, not downtime
• Not patching service keeps old traffic, no downtime

5. In a Jenkins pipeline implementing blue-green deployment, how can you safely clean up the old environment after switching traffic to green?

hard

A. Scale down the blue deployment to zero replicas after verifying green is stable

B. Delete the blue deployment immediately after patching the service

C. Keep both blue and green running indefinitely

D. Restart Jenkins to clear old environment

Solution

1. Step 1: Understand cleanup in blue-green deployment

   After switching traffic, the old environment should be scaled down to free resources but kept until stability is confirmed.

2. Step 2: Identify safe cleanup method in Jenkins pipeline

   Scaling down blue to zero replicas after green is stable avoids downtime and allows rollback if needed.

3. Final Answer:

   Scale down the blue deployment to zero replicas after verifying green is stable -> Option A

4. Quick Check:

   Scale down old env after stable new env [OK]

Hint: Scale down old env only after new env is stable [OK]

Common Mistakes:

• Deleting old deployment immediately risks downtime
• Keeping both running wastes resources
• Restarting Jenkins does not affect deployments