Rollback strategies in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a rollback stage in a Jenkins pipeline.

Jenkins

stage('Rollback') {
    steps {
        sh '[1]'
    }
}

Drag options to blanks, or click blank then click option'

Arollback.sh

Becho Rollback initiated

Cdeploy.sh

Dbuild.sh

Attempts:

3 left

💡 Hint

Common Mistakes

Using deploy.sh instead of rollback.sh

Forgetting to use the shell command

Using echo instead of running a script

The rollback stage runs the rollback.sh script to revert changes.

2fill in blank

medium

Complete the code to trigger rollback only if the deployment fails.

Jenkins

post {
    failure {
        script {
            [1]()
        }
    }
}

Drag options to blanks, or click blank then click option'

Adeploy

Btest

Cbuild

Drollback

Attempts:

3 left

💡 Hint

Common Mistakes

Calling deploy() on failure

Calling build() or test() instead of rollback()

Not calling any function

The rollback() function is called when the deployment fails to revert changes.

3fill in blank

hard

Fix the error in the rollback script call to use the correct Jenkins syntax.

Jenkins

steps {
    [1] 'rollback.sh'
}

Drag options to blanks, or click blank then click option'

Ash

BexecuteShell

CrunShell

Dshell

Attempts:

3 left

💡 Hint

Common Mistakes

Using executeShell or runShell which are not Jenkins steps

Using shell instead of sh

Jenkins uses sh to run shell scripts in pipeline steps.

4fill in blank

hard

Fill both blanks to define a rollback stage that runs a shell script and echoes a message.

Jenkins

stage('Rollback') {
    steps {
        [1] 'rollback.sh'
        [2] 'Rollback completed successfully'
    }
}

Drag options to blanks, or click blank then click option'

Ash

Becho

Crun

Dscript

Attempts:

3 left

💡 Hint

Common Mistakes

Using run instead of sh

Using script instead of echo

Mixing up the order of commands

The sh step runs the rollback script, and echo prints a message.

5fill in blank

hard

Fill all three blanks to create a rollback stage that runs a script, checks a condition, and echoes a message.

Jenkins

stage('Rollback') {
    steps {
        [1] 'rollback.sh'
        script {
            if (currentBuild.result == '[2]') {
                [3] 'Rollback was successful'
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

Ash

BSUCCESS

Cecho

DFAILURE

Attempts:

3 left

💡 Hint

Common Mistakes

Checking for SUCCESS instead of FAILURE

Using run instead of sh

Using print instead of echo

The rollback script runs with sh. The condition checks if the build result is FAILURE. Then echo prints a success message.

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