Rollback strategies in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a rollback strategy in Jenkins?

A rollback strategy in Jenkins is a plan or method to revert an application or system to a previous stable state after a failed deployment or error.

beginner

Name two common rollback strategies used in Jenkins pipelines.

Two common rollback strategies are:
1. Re-deploying the last successful build.
2. Using blue-green deployment to switch traffic back to the stable environment.

intermediate

How can Jenkins pipeline help automate rollback?

Jenkins pipelines can automate rollback by scripting steps to detect failures and trigger deployment of a previous stable build automatically.

intermediate

What is the benefit of using blue-green deployment as a rollback strategy?

Blue-green deployment allows quick rollback by switching user traffic between two identical environments, minimizing downtime and risk.

beginner

What Jenkins feature helps keep track of previous builds for rollback?

Jenkins keeps a history of builds with unique build numbers, allowing easy identification and redeployment of previous stable builds for rollback.

What does a rollback strategy aim to do in Jenkins?

A Increase build speed

B Deploy new features faster

C Revert to a previous stable state after failure

D Monitor server health

Rollback strategies focus on reverting to a stable state after deployment issues.

Which Jenkins feature helps automate rollback?

A Pipeline scripting

B Static code analysis

C User authentication

D Build triggers

Pipeline scripting allows automation of rollback steps on failure.

What is a key advantage of blue-green deployment for rollback?

A Reduces build time

B Requires no extra servers

C Eliminates need for testing

D Switch traffic instantly between environments

Blue-green deployment enables instant traffic switch to a stable environment.

How does Jenkins identify previous builds for rollback?

A By user names

B By unique build numbers

C By server IP

D By deployment time only

Jenkins assigns unique build numbers to track builds.

Which rollback strategy involves redeploying the last successful build?

A Re-deployment rollback

B Blue-green deployment

C Canary release

D Feature toggling

Re-deployment rollback uses the last stable build to revert changes.

Explain how Jenkins pipelines can be used to implement rollback strategies.

Think about how scripts can automate steps after a failed deployment.

Describe the blue-green deployment rollback strategy and its benefits.

Imagine having two identical setups and switching users between them.

Practice

1. What is the main purpose of a rollback strategy in Jenkins deployments?

easy

A. To automatically increase server resources during deployment

B. To speed up the deployment process by skipping tests

C. To revert to a previous stable version when a deployment fails

D. To permanently delete old versions of the application

Solution

1. Step 1: Understand rollback purpose

   Rollback strategies are designed to undo changes when something goes wrong.

2. Step 2: Identify rollback action in Jenkins

   In Jenkins, rollback means returning to a previous stable version to fix deployment issues.

3. Final Answer:

   To revert to a previous stable version when a deployment fails -> Option C

4. Quick Check:

   Rollback = revert to stable version [OK]

Hint: Rollback means going back to a safe version after failure [OK]

Common Mistakes:

• Confusing rollback with speeding up deployment
• Thinking rollback deletes old versions
• Assuming rollback increases server resources

2. Which Jenkins pipeline syntax correctly implements a simple rollback using try-catch?

easy

A. try: deploy() except: rollback()

B. try { deploy() } catch { rollback() }

C. try deploy() catch rollback()

D. try { deploy() } catch (Exception e) { rollback() }

Solution

1. Step 1: Recall Jenkins pipeline syntax

   Jenkins uses Groovy syntax where catch requires an exception parameter.

2. Step 2: Identify correct try-catch structure

   try { deploy() } catch (Exception e) { rollback() } correctly uses catch (Exception e) to catch errors and run rollback.

3. Final Answer:

   try { deploy() } catch (Exception e) { rollback() } -> Option D

4. Quick Check:

   Jenkins try-catch needs exception parameter [OK]

Hint: Jenkins catch needs exception variable in parentheses [OK]

Common Mistakes:

• Omitting exception parameter in catch block
• Using Python-style try-except syntax
• Missing braces around try or catch blocks

3. Given this Jenkins pipeline snippet, what will be the output if deploy() fails?

try {
  deploy()
  echo 'Deployment succeeded'
} catch (Exception e) {
  rollback()
  echo 'Rollback done'
}

medium

A. Rollback done

B. Deployment succeeded

C. No output

D. Deployment succeeded and Rollback done

Solution

1. Step 1: Analyze try block behavior on failure

   If deploy() fails, the code inside try after deploy() is skipped.

2. Step 2: Understand catch block execution

   The catch block runs rollback() and then prints 'Rollback done'.

3. Final Answer:

   Rollback done -> Option A

4. Quick Check:

   Failure triggers catch block output [OK]

Hint: Failed deploy skips try echo, runs catch echo [OK]

Common Mistakes:

• Assuming 'Deployment succeeded' prints on failure
• Thinking both messages print together
• Ignoring catch block execution on error

4. Identify the error in this Jenkins pipeline rollback snippet:

try {
  deploy()
} catch {
  rollback()
}

medium

A. Missing exception parameter in catch block

B. deploy() should be inside catch block

C. rollback() should be outside try-catch

D. try block cannot be used without finally

Solution

1. Step 1: Check catch block syntax in Jenkins

   Jenkins requires catch to have an exception parameter like catch (Exception e).

2. Step 2: Confirm other options are incorrect

   deploy() belongs in try, rollback() in catch is correct, finally is optional.

3. Final Answer:

   Missing exception parameter in catch block -> Option A

4. Quick Check:

   Catch needs exception parameter [OK]

Hint: Catch block must include exception variable [OK]

Common Mistakes:

• Leaving catch parentheses empty
• Moving deploy() into catch block
• Thinking finally is mandatory

5. You want to automate rollback in Jenkins only if deployment fails and the failure is due to a test error. Which approach best achieves this?

hard

A. Always run rollback after deployment regardless of success

B. Use try-catch and check exception message for test failure before rollback

C. Manually trigger rollback after checking logs

D. Skip rollback and notify team on any failure

Solution

1. Step 1: Understand conditional rollback need

   Rollback should run only if failure is due to test errors, not all failures.

2. Step 2: Use try-catch with exception check

   In Jenkins, catch block can inspect exception details to decide if rollback is needed.

3. Step 3: Evaluate other options

   Always running rollback wastes time; manual rollback is slow; skipping rollback misses fixes.

4. Final Answer:

   Use try-catch and check exception message for test failure before rollback -> Option B

5. Quick Check:

   Conditional rollback uses exception checks [OK]

Hint: Check error type in catch before rollback [OK]

Common Mistakes:

• Running rollback unconditionally wastes resources
• Relying on manual rollback delays fixes
• Ignoring failure cause in rollback decision