Feedback loop importance in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage that sends feedback after build.

Jenkins

stage('Feedback') {
    steps {
        [1] 'echo "Build completed, sending feedback"'
    }
}

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

Acheckout

Binput

CarchiveArtifacts

Dsh

Attempts:

3 left

💡 Hint

Common Mistakes

Using input instead of sh for running commands.

The sh step runs shell commands, here used to send feedback via echo.

2fill in blank

medium

Complete the code to trigger a Jenkins pipeline stage only if the build fails, to send failure feedback.

Jenkins

stage('Failure Feedback') {
    when {
        [1] 'FAILURE'
    }
    steps {
        sh 'echo "Build failed, notifying team"'
    }
}

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

Astatus

Bexpression

Cbranch

Denvironment

Attempts:

3 left

💡 Hint

Common Mistakes

Using branch or environment which do not check build status.

The status condition checks the build result status to trigger the stage.

3fill in blank

hard

Fix the error in the Jenkins pipeline snippet to correctly send feedback after tests.

Jenkins

stage('Test Feedback') {
    steps {
        [1] 'echo "Tests passed, sending feedback"'
    }
}

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

Ash

Bbat

Cinput

Dscript

Attempts:

3 left

💡 Hint

Common Mistakes

Using bat on Unix agents causes errors.

The sh step is used to run shell commands on Unix-like agents, correct for sending feedback.

4fill in blank

hard

Fill both blanks to create a post-build action that always sends feedback regardless of build result.

Jenkins

post {
    [1] {
        [2] 'echo "Build finished, sending feedback"'
    }
}

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

Aalways

Bsh

Csuccess

Dfailure

Attempts:

3 left

💡 Hint

Common Mistakes

Using success or failure which run conditionally.

The always block runs regardless of build result, and sh runs the shell command to send feedback.

5fill in blank

hard

Fill all three blanks to define a pipeline that sends feedback only if tests pass and code is on the main branch.

Jenkins

pipeline {
    agent any
    stages {
        stage('Test') {
            steps {
                sh 'run tests'
            }
        }
        stage('Feedback') {
            when {
                [1] 'SUCCESS'
                [2] 'main'
            }
            steps {
                [3] 'echo "Tests passed on main, sending feedback"'
            }
        }
    }
}

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

Astatus

Bbranch

Csh

Denvironment

Attempts:

3 left

💡 Hint

Common Mistakes

Using environment instead of branch for branch condition.

The status condition checks for success, branch checks the branch name, and sh runs the feedback command.

Practice

1. Why is a feedback loop important in Jenkins pipelines?

easy

A. It quickly informs you if your code or build needs fixing

B. It slows down the build process to check for errors

C. It automatically fixes bugs in the code

D. It deletes old builds to save space

Solution

1. Step 1: Understand feedback loop purpose

   A feedback loop gives fast information about the success or failure of a process.

2. Step 2: Apply to Jenkins pipelines

   In Jenkins, feedback loops tell you quickly if your build or tests passed or failed.

3. Final Answer:

   It quickly informs you if your code or build needs fixing -> Option A

4. Quick Check:

   Feedback loop = fast info on success/failure [OK]

Hint: Feedback loops give fast success/failure info [OK]

Common Mistakes:

• Thinking feedback loops fix bugs automatically
• Confusing feedback loops with build speed control
• Assuming feedback loops delete old builds

2. Which Jenkins pipeline syntax correctly adds a feedback step after a stage?

easy

A. steps { post { echo 'Build finished' } }

B. stage { post { echo 'Build finished' } }

C. pipeline { post { stage { echo 'Build finished' } } }

D. post { always { echo 'Build finished' } }

Solution

1. Step 1: Recall Jenkins post block usage

   The post block is used after stages or pipelines to run actions based on build results.

2. Step 2: Identify correct syntax

   post { always { echo 'Build finished' } } correctly uses post { always { ... } } after a stage or pipeline to give feedback.

3. Final Answer:

   post { always { echo 'Build finished' } } -> Option D

4. Quick Check:

   post block syntax = post { always { echo 'Build finished' } } [OK]

Hint: Use post { always { ... } } after stages for feedback [OK]

Common Mistakes:

• Placing post inside steps block
• Using post without always or condition
• Misplacing post inside stage incorrectly

3. What will Jenkins output after this pipeline runs successfully?

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
      post {
        success {
          echo 'Build succeeded!'
        }
      }
    }
  }
}

medium

A. Building...
Build succeeded!

B. Build succeeded!
Building...

C. Building...

D. Build failed!

Solution

1. Step 1: Read pipeline steps and post block

   The pipeline prints 'Building...' during the build stage steps.

2. Step 2: Check post success block

   After successful build, it prints 'Build succeeded!'.

3. Final Answer:

   Building... Build succeeded! -> Option A

4. Quick Check:

   Steps then post success message = Building... Build succeeded! [OK]

Hint: Post success runs after steps if build passes [OK]

Common Mistakes:

• Thinking post runs before steps
• Ignoring post success block
• Confusing output order

4. Identify the error in this Jenkins pipeline snippet that prevents feedback after the stage:

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        echo 'Testing...'
      }
      post {
        always echo 'Tests done'
      }
    }
  }
}

medium

A. Incorrect stage name 'Test'

B. Missing braces {} around the always block commands

C. Missing agent declaration

D. Using echo inside steps is invalid

Solution

1. Step 1: Check post block syntax

   The always block must have braces {} around its commands.

2. Step 2: Identify missing braces

   Here, always echo 'Tests done' lacks braces, causing syntax error.

3. Final Answer:

   Missing braces {} around the always block commands -> Option B

4. Quick Check:

   post always needs braces {} [OK]

Hint: Always use braces {} in post conditions [OK]

Common Mistakes:

• Forgetting braces in post blocks
• Thinking stage name affects feedback
• Ignoring agent declaration errors

5. You want Jenkins to notify your team immediately after any pipeline stage finishes, regardless of success or failure. Which pipeline snippet correctly implements this feedback loop?

hard

A. stage('Deploy') {
steps {
echo 'Deploying...'
}
post {
success {
mail to: '[e-mail]', subject: 'Deploy Success'
}
}
}

B. stage('Deploy') {
steps {
echo 'Deploying...'
}
post {
failure {
mail to: '[e-mail]', subject: 'Deploy Failed'
}
}
}

C. stage('Deploy') {
steps {
echo 'Deploying...'
}
post {
always {
mail to: '[e-mail]', subject: 'Deploy Finished'
}
}
}

D. stage('Deploy') {
steps {
echo 'Deploying...'
}
post {
changed {
mail to: '[e-mail]', subject: 'Deploy Status Changed'
}
}
}

Solution

1. Step 1: Understand requirement for notification

   The team wants notification after any stage finish, success or failure.

2. Step 2: Identify correct post condition

   The always block runs after every stage completion regardless of result.

3. Step 3: Compare options

   stage('Deploy') { steps { echo 'Deploying...' } post { always { mail to: '[e-mail]', subject: 'Deploy Finished' } } } uses post { always { ... } } with mail notification, matching the requirement.

4. Final Answer:

   post { always { mail ... } } -> Option C

5. Quick Check:

   Notify always after stage = stage('Deploy') { steps { echo 'Deploying...' } post { always { mail to: '[e-mail]', subject: 'Deploy Finished' } } } [OK]

Hint: Use post { always { ... } } for all outcomes feedback [OK]

Common Mistakes:

• Using success or failure only misses some cases
• Using changed triggers only on status changes
• Forgetting braces in post blocks