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 Delete Job operation under the Job Management resource allows users to delete an existing Jenkins job by its name.
Typical use cases include:
- Automating cleanup of obsolete or temporary Jenkins jobs.
- Managing Jenkins jobs programmatically as part of CI/CD workflows.
- Integrating Jenkins job lifecycle management into broader automation pipelines.
For example, you might use this node to automatically remove a Jenkins job after a project is archived or when cleaning up test jobs created dynamically.
Properties
| Name | Meaning |
|---|---|
| Job Name | The exact name of the Jenkins job to delete. This is a required string input. |
Output
The output JSON contains a simple status confirmation indicating whether the deletion was successful. It looks like:
[
{
"status": "success"
}
]
No binary data is produced by this operation.
Dependencies
- Requires a Jenkins server accessible via HTTP(S).
- Needs an API authentication token or credentials configured in n8n to authenticate requests to Jenkins.
- The node uses Jenkins REST API endpoints to perform operations.
- The base URL of the Jenkins instance must be provided in the credentials.
Troubleshooting
- No credentials found: The node will throw an error if Jenkins credentials are not set up or missing. Ensure that valid API authentication details are configured in n8n.
- Job not found or invalid job name: If the specified job name does not exist on the Jenkins server, the API call may fail or return an error. Verify the job name spelling and existence.
- Permission denied: The Jenkins user associated with the API token must have permission to delete jobs. Lack of permissions will cause errors.
- Network issues: Connectivity problems between n8n and Jenkins will result in request failures. Check network access and firewall settings.
- Unexpected response format: If Jenkins is customized or behind proxies altering responses, the node might not parse results correctly.