Jenkins Community Node icon

Jenkins Community Node

Jenkins Node

Actions16

Overview

The node integrates with Jenkins, a popular automation server used for continuous integration and delivery. Specifically, the "Job Management" resource with the "Get Job Details" operation allows users to retrieve detailed information about a specific Jenkins job by its name.

This node is beneficial in scenarios where you want to programmatically monitor or audit Jenkins jobs, fetch their configurations, or integrate Jenkins job data into broader workflows. For example, you might use it to:

  • Automatically fetch job status and details before triggering downstream processes.
  • Audit job configurations regularly to ensure compliance.
  • Display job metadata within dashboards or reports.

Properties

Name Meaning
Job Name The exact name of the Jenkins job for which details are to be retrieved. This is required.

Output

The output is a JSON object containing all the details of the specified Jenkins job as returned by the Jenkins API endpoint /job/{jobName}/api/json. This typically includes metadata such as job description, build history, parameters, triggers, and other configuration details.

Example structure (simplified):

{
  "name": "example-job",
  "url": "http://jenkins.example.com/job/example-job/",
  "color": "blue",
  "builds": [...],
  "lastBuild": {...},
  "property": [...],
  ...
}

No binary data is output for this operation.

Dependencies

  • Requires an active Jenkins server accessible via a base URL.
  • Needs an API authentication token or credentials configured in n8n to authenticate requests to Jenkins.
  • The node uses HTTP requests authenticated with these credentials to interact with Jenkins REST API.

Troubleshooting

  • No credentials found: Ensure that Jenkins API credentials are properly set up in n8n and linked to the node.
  • Job not found or invalid job name: Verify that the job name exactly matches a job on your Jenkins server, including case sensitivity.
  • Network errors or timeouts: Confirm network connectivity to the Jenkins server and that the base URL is correct.
  • Permission denied or unauthorized: Check that the API token or credentials have sufficient permissions to access job details.
  • Unexpected response format: If Jenkins is customized or uses plugins that alter API responses, the node may not parse the data correctly.

Links and References

Discussion