Post-build actions in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Post-build Actions in Jenkins

Which of the following best describes the purpose of post-build actions in a Jenkins job?

A They specify tasks that run after the build completes, such as notifications or archiving artifacts.

B They define the steps to compile and build the source code before testing.

C They configure the source code repository and branch to build from.

D They set environment variables used during the build process.

💡 Hint

Think about what happens after the build finishes successfully or fails.

Post-build actions are tasks Jenkins performs after the build steps, like sending emails, archiving files, or triggering other jobs.

💻 Command Output

intermediate

Result of Archiving Artifacts Post-build

After configuring a Jenkins job to archive the file output.log as a post-build action, what will you see in the Jenkins job page after a successful build?

A The <code>output.log</code> file will be available for download under the 'Archived Artifacts' section.

B The build will fail because archiving is not allowed in post-build actions.

C The <code>output.log</code> file will be deleted from the workspace automatically.

D The console output will include the contents of <code>output.log</code>.

💡 Hint

Archiving artifacts means saving files for later access from the build page.

Archiving artifacts stores specified files so users can download them from the build page after completion.

🔀 Workflow

advanced

Configuring Email Notification as a Post-build Action

You want Jenkins to send an email notification only when a build fails. Which post-build action configuration achieves this?

A Add 'Post-build Script' to run a shell command that sends email regardless of build status.

B Add 'Editable Email Notification' post-build action and set triggers to 'Failure'.

C Add 'Send Email' build step before the build starts.

D Add 'Email Notification' post-build action and leave triggers empty.

💡 Hint

Look for a post-build action that supports conditional triggers.

The 'Editable Email Notification' plugin allows setting triggers like 'Failure' to send emails only on failed builds.

❓ Troubleshoot

advanced

Troubleshooting Post-build Action Failure

A Jenkins job's post-build action to archive artifacts is not working; no files appear under 'Archived Artifacts' after a successful build. What is the most likely cause?

A The build steps did not run because the job was disabled.

B The Jenkins master node is offline.

C The file pattern specified for archiving does not match any files in the workspace.

D The post-build action is configured before the build steps.

💡 Hint

Check if the files you want to archive actually exist after the build.

If the file pattern does not match any files, Jenkins archives nothing, so no artifacts appear.

✅ Best Practice

expert

Best Practice for Post-build Actions in Pipeline Scripts

In a Jenkins Pipeline script, which is the best way to ensure a post-build action runs regardless of build success or failure?

A Place the post-build action commands at the start of the <code>pipeline</code> block.

B Add post-build actions only in the Jenkins job configuration UI, not in the pipeline script.

C Use <code>try { ... } catch { ... }</code> blocks inside the <code>stages</code> to run post-build actions.

D Use the <code>post { always { ... } }</code> block to define actions that always run after the build.

💡 Hint

Look for a pipeline syntax that guarantees execution after all stages.

The post { always { ... } } block runs its steps no matter if the build succeeded, failed, or was aborted.