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 Build Management - Get Build operation retrieves detailed information about a specific build of a Jenkins job.
Typical use cases include:
- Fetching the status and metadata of a particular build to monitor CI/CD pipelines.
- Integrating Jenkins build data into workflows for reporting or triggering downstream processes.
- Automating quality gates by checking build results before proceeding.
For example, you might use this node to get the details of build number 42 of a job named "MyApp-Build" to verify if it succeeded or failed.
Properties
| Name | Meaning |
|---|---|
| Job Name | The name of the Jenkins job whose build you want to query. |
| Build Number | The specific build number of the job to retrieve details for (e.g., "1", "42"). |
Output
The output is a JSON object containing all the details of the specified Jenkins build as returned by the Jenkins API. This typically includes:
- Build metadata such as build number, status, duration, timestamp.
- Information about the build result (success, failure, etc.).
- Details about the changes included in the build.
- Any other Jenkins-specific build properties.
The output is returned as an array of JSON objects, each representing one build detail response.
No binary data is produced by this operation.
Dependencies
- Requires a Jenkins server URL and valid API authentication credentials (an API key or token).
- The node expects these credentials to be configured in n8n under a generic API authentication credential type.
- Network access to the Jenkins server must be available from the n8n instance.
Troubleshooting
- No credentials found: Ensure that Jenkins API credentials are properly set up in n8n and linked to the node.
- 404 Not Found errors: Verify that the job name and build number exist on the Jenkins server.
- Authentication errors: Check that the API token or key has sufficient permissions to access build details.
- Network timeouts: Confirm network connectivity between n8n and Jenkins server.
- Invalid build number format: The build number should be a string representing a positive integer.