Actions16
- Build Management Actions
- Job Management Actions
Overview
This node integrates with Jenkins, a popular automation server used for continuous integration and delivery. Specifically, the "Get Last Failed Build" operation under the "Build Management" resource retrieves details about the most recent build of a specified Jenkins job that ended in failure.
Use cases include:
- Monitoring Jenkins jobs to detect failures quickly.
- Triggering alerts or downstream workflows when a build fails.
- Fetching failure details for reporting or debugging purposes.
For example, you can use this node to automatically fetch the last failed build information of a critical deployment job and notify your team via email or chat.
Properties
| Name | Meaning |
|---|---|
| Job Name | The exact name of the Jenkins job for which to retrieve the last failed build details. |
Output
The node outputs JSON data representing the details of the last failed build for the specified job. This includes all metadata Jenkins provides about that build, such as build number, status, timestamps, changes, and more.
The output is structured as an array of JSON objects (usually one object), each containing the full build information returned by Jenkins' API endpoint /job/{jobName}/lastFailedBuild/api/json.
No binary data is output for this operation.
Dependencies
- Requires a Jenkins server accessible via its base URL.
- Needs an API authentication token or credentials configured in n8n to authenticate requests to Jenkins.
- The node uses HTTP requests authenticated with these credentials to interact with Jenkins REST API.
Troubleshooting
- No credentials found: Ensure you have configured valid Jenkins API credentials in n8n before running the node.
- Job not found or incorrect job name: Verify the job name is correct and exists on the Jenkins server.
- Network or authentication errors: Check network connectivity to Jenkins and confirm the API token or credentials are valid.
- Empty or no failed builds: If the job has no failed builds, the API may return an error or empty response; handle this case gracefully in your workflow.