Blue-green deployment pattern in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Blue-Green Deployment Basics

What is the main advantage of using the blue-green deployment pattern in Jenkins pipelines?

A It merges code branches automatically before deployment.

B It allows zero downtime by switching traffic between two identical environments.

C It encrypts all deployment artifacts for security.

D It automatically scales the application based on user load.

💡 Hint

Think about how user traffic is managed during deployment.

Blue-green deployment uses two identical environments (blue and green). One serves live traffic while the other is updated. Switching traffic avoids downtime.

💻 Command Output

intermediate

Jenkins Pipeline Step Output

Given this Jenkins pipeline snippet for blue-green deployment, what will be the output of the sh step?

stage('Switch Traffic') {
  steps {
    sh 'echo Switching traffic to green environment'
  }
}

A Switching traffic to green environment

B Error: Unknown command 'echo Switching traffic to green environment'

C No output, the step is skipped

D Switching traffic to blue environment

💡 Hint

What does the sh step do in Jenkins pipelines?

The sh step runs shell commands and prints their output. Here it echoes the message about switching traffic.

❓ Configuration

advanced

Correct Jenkinsfile Snippet for Blue-Green Deployment

Which Jenkinsfile snippet correctly implements switching traffic from blue to green environment using environment variables?

A

environment {
  ACTIVE_ENV = 'green'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl set image deployment/myapp myapp-container=myapp:${ACTIVE_ENV}"
  }
}

B

environment {
  ACTIVE_ENV = 'blue'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl set image deployment/myapp myapp-container=myapp:${ACTIVE_ENV}"
  }
}

C

environment {
  ACTIVE_ENV = 'red'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl set image deployment/myapp myapp-container=myapp:${ACTIVE_ENV}"
  }
}

D

environment {
  ACTIVE_ENV = 'green'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl rollout restart deployment/myapp"
  }
}

💡 Hint

Focus on the environment variable value that matches the target environment for traffic switch.

Setting ACTIVE_ENV to 'green' and updating the deployment image to use that environment switches traffic correctly. 'red' is invalid and 'blue' would switch back.

❓ Troubleshoot

advanced

Troubleshooting Traffic Switch Failure

After running a blue-green deployment pipeline, users report downtime. Which Jenkins pipeline issue is the most likely cause?

A The pipeline used the correct environment variable for switching traffic.

B The pipeline skipped the deployment stage entirely.

C The pipeline switched traffic before the green environment was fully ready.

D The pipeline used a shell command to echo status messages.

💡 Hint

Think about what happens if traffic is switched too early.

If traffic switches before the new environment is ready, users experience downtime or errors. Proper readiness checks prevent this.

🔀 Workflow

expert

Blue-Green Deployment Workflow Steps

Arrange the following steps in the correct order for a blue-green deployment pipeline in Jenkins.

A 3,1,2,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about deploying first, then testing, then switching traffic, then monitoring.

The correct order is to deploy to the inactive environment, test it, switch traffic, then monitor for issues to ensure smooth deployment.

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