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 Artifact operation allows users to retrieve a specific artifact file from a particular build of a Jenkins job.
Typical use cases include:
- Downloading build reports, logs, or compiled binaries generated by Jenkins jobs.
- Automating retrieval of build outputs for further processing or deployment in workflows.
- Archiving or analyzing artifacts produced by CI/CD pipelines.
For example, after triggering a build in Jenkins, you can use this node to fetch the resulting test report HTML file or a packaged application binary for distribution.
Properties
| Name | Meaning |
|---|---|
| Job Name | The name of the Jenkins job that produced the build. |
| Build Number | The specific build number from which to retrieve the artifact (e.g., "1", "42"). |
| Artifact Path | The path within the build's artifacts directory where the desired artifact is located. |
| Artifact Output Name | The filename to assign to the downloaded artifact in the node's output (e.g., "report.html"). |
Output
The node outputs the requested artifact as binary data attached to the output item. The output structure includes:
jsonfield: Contains a key named after the specified artifact output name, holding the raw content of the artifact as a string.binaryfield: Contains the artifact file as binary data, accessible by the same artifact output name.
This allows downstream nodes to access the artifact either as raw JSON text or as binary data suitable for saving to disk or further processing.
Dependencies
- Requires a Jenkins server URL and valid API authentication credentials (such as an API token or username/password) configured in n8n.
- The node uses HTTP requests authenticated via these credentials to interact with the Jenkins REST API.
- No additional external libraries beyond those bundled with n8n are required.
Troubleshooting
- No credentials found: Ensure that Jenkins API credentials are properly set up and linked to the node.
- Artifact not found or 404 error: Verify the correctness of the job name, build number, and artifact path. The artifact must exist in the specified build.
- Permission denied or authentication errors: Check that the Jenkins user associated with the credentials has permission to access the job and its artifacts.
- Binary data issues: If the artifact is large or binary, ensure that subsequent nodes can handle binary data correctly.