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 resource with the Get Build Console Output operation allows users to retrieve the console output (log) of a specific build of a Jenkins job.
Typical use cases include:
- Fetching the detailed logs of a particular build to analyze build results or diagnose failures.
- Automating monitoring workflows where build outputs are checked programmatically.
- Archiving or processing build logs as part of a larger CI/CD pipeline.
For example, after triggering a build in Jenkins, you can use this node to get the console output of that build number to verify success or extract error messages.
Properties
| Name | Meaning |
|---|---|
| Job Name | The name of the Jenkins job whose build console output you want to retrieve. |
| Build Number | The specific build number of the job to get the console output from. |
Output
The node outputs JSON data containing the console output text of the specified build under the field:
{
"output": "<console log string>"
}
This is a plain text string representing the full console log of the build.
No binary data output 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 Jenkins server must be accessible from the n8n instance running this node.
Troubleshooting
- No credentials found: Ensure that the Jenkins API authentication token or credentials are properly set up in n8n.
- 404 Not Found or similar HTTP errors: Verify that the job name and build number exist on the Jenkins server.
- Empty or incomplete console output: Confirm that the build has completed or at least started producing logs.
- Network issues: Make sure the Jenkins server URL is reachable from your n8n environment.