Why notifications matter in Jenkins - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send an email notification after a Jenkins build.

Jenkins

post {
  always {
    emailext [1] {
      to: '[e-mail]'
      subject: 'Build Notification'
      body: 'The build has completed.'
    }
  }
}

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

Amail

Bnotify

Cemail

Dsend

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'notify' instead of 'send' causes a syntax error.

Using 'mail' is a different step and not part of emailext.

The emailext send step triggers the email notification in Jenkins pipelines.

2fill in blank

medium

Complete the code to notify only when the build fails.

Jenkins

post {
  [1] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build Failed'
      body: 'Please check the build logs.'
    }
  }
}

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

Asuccess

Balways

Cfailure

Dunstable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'always' sends notifications every time.

Using 'success' sends notifications only on success.

The failure block runs only when the build fails, triggering the notification.

3fill in blank

hard

Fix the error in the notification block to correctly send an email on unstable builds.

Jenkins

post {
  unstable {
    emailext [1] {
      to: '[e-mail]'
      subject: 'Build Unstable'
      body: 'The build is unstable.'
    }
  }
}

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

Asend

Bnotify

Cemail

Dmail

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'notify' or 'email' causes the pipeline to fail.

Using 'mail' is a different plugin step.

The correct step to send emails with the emailext plugin is send.

4fill in blank

hard

Fill both blanks to send notifications only when the build is successful and unstable.

Jenkins

post {
  [1] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build Success'
      body: 'The build succeeded.'
    }
  }
  [2] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build Unstable'
      body: 'The build is unstable.'
    }
  }
}

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

Asuccess

Bfailure

Cunstable

Dalways

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'failure' instead of 'success' sends notifications on failure.

Using 'always' sends notifications every time.

The success block runs on successful builds, and unstable runs on unstable builds, sending notifications accordingly.

5fill in blank

hard

Fill all three blanks to send notifications with dynamic subject and body based on build status.

Jenkins

post {
  [1] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build [2]'
      body: 'The build status is [3].'
    }
  }
}

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

Afailure

Bsuccess

CFAILED

DSUCCESS

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing failure block with success messages.

Using lowercase status words in subject and body.

When the build is successful, the success block runs, and the subject and body reflect the success status.