Actions16
- Build Management Actions
- Job Management Actions
Overview
The node integrates with Jenkins, a popular automation server used for continuous integration and delivery. Specifically, the Stop Build operation under the Build Management resource allows users to stop a running build of a specified Jenkins job.
This is useful in scenarios where a build is no longer needed, is stuck, or needs to be aborted due to errors or changed requirements. For example, if a deployment pipeline triggers a build that later fails a quality gate, this node can be used to halt the build process immediately.
Properties
| Name | Meaning |
|---|---|
| Job Name | The name of the Jenkins job whose build you want to stop. |
| Build Number | The specific build number of the job to stop. |
Output
The output JSON contains a simple status confirmation indicating whether the stop request was successful. It looks like:
{
"status": "success"
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Jenkins server.
- Needs the Jenkins base URL configured in the credentials.
- The node uses HTTP requests authenticated via the provided API key to communicate with Jenkins REST API endpoints.
Troubleshooting
- No credentials found: The node will throw an error if Jenkins credentials are not set up or accessible. Ensure the API key credential is properly configured.
- Invalid Job Name or Build Number: If the job name or build number does not exist on the Jenkins server, the HTTP request will fail. Verify these inputs carefully.
- Permission Denied: The API key must have sufficient permissions to stop builds on the Jenkins server.
- Network Issues: Connectivity problems between n8n and Jenkins will cause request failures. Check network access and firewall settings.
- Unexpected Response: If Jenkins returns an error or unexpected response, verify the Jenkins server logs for more details.