Скачать или смотреть How to Execute a Job and Get Its Status in Jenkins Pipeline

Learn how to execute a job in Jenkins Pipeline and retrieve its status effectively. Follow our step-by-step guide to ensure your pipeline works seamlessly.
---
This video is based on the question https://stackoverflow.com/q/68143614/ asked by the user 'Roman Zinger' ( https://stackoverflow.com/u/13105157/ ) and on the answer https://stackoverflow.com/a/68145107/ provided by the user 'Dashrath Mundkar' ( https://stackoverflow.com/u/8053714/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Jenkins pipeline execute job and get status

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Execute a Job and Get Its Status in Jenkins Pipeline: A Complete Guide

In the world of Continuous Integration and Continuous Deployment (CI/CD), Jenkins is a powerful tool that allows you to automate tasks related to building, testing, and deploying software. One common requirement in Jenkins pipelines is to execute another job and check its execution status. This guide will guide you through the process of executing a job in a Jenkins pipeline and retrieving its status effectively.

Understanding the Problem

When you’re working with Jenkins pipelines, you might find yourself needing to execute an existing job from within another job or pipeline. After triggering this job, you'll want to check if it succeeded or failed. Below is a simplified version of a scenario you might encounter:

[[See Video to Reveal this Text or Code Snippet]]

In this example, while the intention is correct, the syntax and method for checking the job's execution status are not.

Solution Overview

Key Improvements

Use getResult(): Instead of checking the status property directly, you should utilize the getResult() method to retrieve the status of the job.

Correct Status Check: The correct status string to check for a failure is FAILURE, not Failed.

With these improvements in mind, the corrected code for your Jenkins Pipeline should look like this:

[[See Video to Reveal this Text or Code Snippet]]

Breakdown of the Code

Defining the Pipeline: This begins with the pipeline block that specifies the agent configuration.

Agent Configuration: The agent { label 'master' } line indicates where the pipeline will run (in this case, on the master node).

Stages: The stages block consists of one or more stages where you define the steps to be executed.

Executing a Job:

def job_exec_details = build job: 'build_job', propagate: false, wait: true: This line executes the specified job (build_job). The propagate: false option allows the current pipeline to continue without failing if the triggered job fails, while wait: true ensures that the current job waits for build_job to finish before moving on.

Checking Job Status:

if (job_exec_details.getResult() == 'FAILURE'): This checks the result of the executed job. If it resulted in a failure, it executes the code within the if block.

Output:

echo "JOB FAILED": This outputs a message to the console indicating the job failed, which can be useful for debugging and logging purposes.

Conclusion

Retrieving the status of a job executed within a Jenkins pipeline is straightforward once you understand how to use the correct methods and properties. By implementing the changes outlined above, you enhance your pipeline's ability to handle job results effectively, ensuring better error handling and reporting.

Feel free to adapt this structure to your specific needs in Jenkins and continue to streamline your CI/CD processes!