Hybrid CI/CD approaches in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage named 'Build'.

Jenkins

stage('[1]') {
    steps {
        echo 'Building the project'
    }
}

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

ABuild

BTest

CDeploy

DClean

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong stage name like 'Test' instead of 'Build'.

The stage name should be 'Build' to represent the build step in the pipeline.

2fill in blank

medium

Complete the code to trigger a Jenkins pipeline only when a commit is pushed to the 'main' branch.

Jenkins

pipeline {
    agent any
    triggers {
        pollSCM('[1]')
    }
    stages {
        stage('Build') {
            steps {
                echo 'Building...'
            }
        }
    }
}

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

Amain

Brefs/heads/main

CH/5 * * * *

D*/15 * * * *

Attempts:

3 left

💡 Hint

Common Mistakes

Using branch names like 'refs/heads/main' as pollSCM argument.

The trigger should specify a cron expression for polling SCM, such as 'H/5 * * * *'. Branch filtering is not done in pollSCM but in SCM configuration.

3fill in blank

hard

Fix the error in the Jenkins pipeline code to correctly define an environment variable.

Jenkins

pipeline {
    agent any
    environment {
        VERSION = '[1]'
    }
    stages {
        stage('Build') {
            steps {
                echo "Version is $VERSION"
            }
        }
    }
}

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

A"1.0.0"

B1.0.0

CVERSION=1.0.0

D'1.0.0'

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning unquoted values causing syntax errors.

Environment variables in Jenkinsfile should be assigned string values with single quotes.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline stage that runs tests only if the build stage succeeds.

Jenkins

stage('Test') {
    when {
        [1] [2] 'Build'
    }
    steps {
        echo 'Running tests'
    }
}

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

Astage

Bbranch

Cequals

DnotEquals

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'branch' instead of 'stage' in the when condition.

The 'when' condition uses 'stage' and 'equals' to check if the 'Build' stage succeeded.

5fill in blank

hard

Fill all three blanks to define a hybrid Jenkins pipeline that uses both scripted and declarative syntax.

Jenkins

pipeline {
    agent any
    stages {
        stage('Hybrid') {
            steps {
                script {
                    if (env.BRANCH_NAME == '[1]') {
                        echo '[2]'
                    } else {
                        echo '[3]'
                    }
                }
            }
        }
    }
}

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

Amain

BRunning on main branch

CRunning on feature branch

Ddevelop

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong branch names or messages that don't match the condition.

The script checks if the branch is 'main' and echoes the appropriate message for main or feature branches.

Practice

1. What is the main purpose of using a hybrid CI/CD approach in Jenkins pipelines?

easy

A. To combine automatic and manual steps for safer deployments

B. To run only manual deployment steps without automation

C. To automate all steps without any manual intervention

D. To disable pipeline triggers and run jobs manually

Solution

1. Step 1: Understand hybrid CI/CD concept

   Hybrid CI/CD mixes automatic and manual steps to balance speed and control.

2. Step 2: Identify Jenkins pipeline usage

   Jenkins pipelines use the input step to pause for manual approval, enabling safer deployments.

3. Final Answer:

   To combine automatic and manual steps for safer deployments -> Option A

4. Quick Check:

   Hybrid CI/CD = mix auto + manual [OK]

Hint: Hybrid means mixing auto and manual steps [OK]

Common Mistakes:

• Thinking hybrid means fully manual
• Assuming hybrid means fully automated
• Confusing hybrid with disabling triggers

2. Which Jenkins pipeline syntax correctly adds a manual approval step?

easy

A. manualApproval('Approve deployment?')

B. input message: 'Approve deployment?'

C. pause('Approve deployment?')

D. waitForInput('Approve deployment?')

Solution

1. Step 1: Recall Jenkins input step syntax

   The input step pauses the pipeline and asks for manual approval with a message.

2. Step 2: Match syntax to options

   Only input message: 'Approve deployment?' is valid Jenkins pipeline syntax for manual input.

3. Final Answer:

   input message: 'Approve deployment?' -> Option B

4. Quick Check:

   Jenkins manual step = input message [OK]

Hint: Use 'input message:' for manual approval in Jenkins [OK]

Common Mistakes:

• Using non-existent commands like manualApproval
• Confusing input with pause or waitForInput
• Missing the 'message:' keyword

3. Given this Jenkins pipeline snippet, what happens when it runs?

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
    stage('Deploy') {
      steps {
        input message: 'Approve deployment?'
        echo 'Deploying...'
      }
    }
  }
}

medium

A. Pipeline fails because input step is invalid

B. Build and deploy run automatically without pause

C. Deploy runs first, then build runs after approval

D. Build runs, then pipeline waits for manual approval before deploying

Solution

1. Step 1: Analyze pipeline stages order

   Stages run in order: 'Build' first, then 'Deploy'.

2. Step 2: Understand input step effect

   The input step pauses the pipeline and waits for manual approval before continuing to echo 'Deploying...'.

3. Final Answer:

   Build runs, then pipeline waits for manual approval before deploying -> Option D

4. Quick Check:

   input pauses pipeline for approval [OK]

Hint: Input pauses pipeline until manual approval [OK]

Common Mistakes:

• Assuming deploy runs automatically without pause
• Thinking input step causes failure
• Confusing stage order

4. You added this input step in your Jenkins pipeline but it never pauses for approval:

input 'Approve deployment?'

What is the likely problem?

medium

A. The input step requires a named parameter like message: to work

B. The input step must be inside a script block

C. The input step only works in declarative pipelines

D. The input step needs a timeout parameter

Solution

1. Step 1: Check input step syntax

   The input step requires named parameters like message: 'text' for proper execution.

2. Step 2: Identify missing named parameter

   Using just a string without message: causes Jenkins to ignore the input step and not pause.

3. Final Answer:

   The input step requires a named parameter like message: to work -> Option A

4. Quick Check:

   Input needs message: parameter [OK]

Hint: Always use 'message:' with input step [OK]

Common Mistakes:

• Omitting message: parameter
• Thinking input must be in script block
• Assuming timeout is mandatory

5. You want a Jenkins pipeline that builds automatically, then waits for manual approval, and finally deploys only if approved within 10 minutes. Which snippet correctly implements this hybrid CI/CD approach?

hard

A. timeout(time: 10, unit: MINUTES) {
input message: 'Approve deployment?'
}
echo 'Deploying...'

B. input message: 'Approve deployment?', timeout: 10, unit: 'MINUTES'
if (currentBuild.result != 'ABORTED') {
echo 'Deploying...'
}

C. timeout(time: 10, unit: 'MINUTES') {
input message: 'Approve deployment?'
echo 'Deploying...'
}

D. input message: 'Approve deployment?', timeout: 10, unit: 'MINUTES'
echo 'Deploying...'

Solution

1. Step 1: Understand timeout with input step

   To limit approval wait time, wrap input and deployment steps inside a timeout block.

2. Step 2: Check which option wraps input and deploy inside timeout

   timeout(time: 10, unit: 'MINUTES') { input message: 'Approve deployment?' echo 'Deploying...' } wraps both input and echo 'Deploying...' inside timeout, ensuring deploy runs only if approved within 10 minutes.

3. Final Answer:

   timeout(time: 10, unit: 'MINUTES') { input message: 'Approve deployment?' echo 'Deploying...' } -> Option C

4. Quick Check:

   Timeout wraps input and deploy steps [OK]

Hint: Wrap input and deploy in timeout block [OK]

Common Mistakes:

• Not wrapping deploy inside timeout
• Checking build result incorrectly
• Using timeout only around input without deploy