Rollback strategies in Jenkins - Mini Project: Build & Apply

Implementing a Basic Rollback Strategy in Jenkins Pipeline

📖 Scenario: You are working as a DevOps engineer. Your team uses Jenkins to deploy applications. Sometimes deployments fail, and you need a way to quickly go back to the last working version. This is called a rollback.In this project, you will create a simple Jenkins pipeline script that deploys an application and rolls back if the deployment fails.

🎯 Goal: Build a Jenkins pipeline script that deploys an application, checks if the deployment succeeded, and if not, rolls back to the previous stable version.

📋 What You'll Learn

Create a variable to hold the current application version

Add a variable for the previous stable version

Write a conditional step to check deployment success

Print the deployment or rollback result

💡 Why This Matters

🌍 Real World

Rollback strategies are essential in real deployments to quickly recover from failed releases and keep applications stable.

💼 Career

Understanding rollback in Jenkins pipelines is a key skill for DevOps engineers to maintain reliable continuous delivery.

1

Setup Application Versions

Create two variables in the Jenkins pipeline script: currentVersion set to "1.2.0" and previousVersion set to "1.1.5".

Jenkins

# Your code here

Hint

Use def to declare variables inside the script block.

2

Add Deployment Status Variable

Inside the script block, add a variable called deploymentSuccess and set it to false to simulate a failed deployment.

Jenkins

pipeline {
    agent any
    stages {
        stage('Setup Versions') {
            steps {
                script {
                    def currentVersion = "1.2.0"
                    def previousVersion = "1.1.5"
                    // Your code here
                }
            }
        }
    }
}

Hint

Set deploymentSuccess to false to simulate failure.

3

Add Rollback Logic

Inside the script block, write an if statement that checks deploymentSuccess. If it is false, set a variable deployedVersion to previousVersion. Otherwise, set deployedVersion to currentVersion.

Jenkins

pipeline {
    agent any
    stages {
        stage('Setup Versions') {
            steps {
                script {
                    def currentVersion = "1.2.0"
                    def previousVersion = "1.1.5"
                    def deploymentSuccess = false
                    // Add if statement to set deployedVersion
                }
            }
        }
    }
}

Hint

Use if (!deploymentSuccess) to check if deployment failed.

4

Print Deployment Result

Add a println statement inside the script block to print "Deployed version: " followed by the deployedVersion variable.

Jenkins

pipeline {
    agent any
    stages {
        stage('Setup Versions') {
            steps {
                script {
                    def currentVersion = "1.2.0"
                    def previousVersion = "1.1.5"
                    def deploymentSuccess = false
                    def deployedVersion
                    if (!deploymentSuccess) {
                        deployedVersion = previousVersion
                    } else {
                        deployedVersion = currentVersion
                    }
                    // Print the deployed version
                }
            }
        }
    }
}

Hint

Use println("Deployed version: ${deployedVersion}") to print the result.

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