Jenkins Community Node icon

Jenkins Community Node

Jenkins Node

Actions16

Overview

This node integrates with Jenkins, a popular automation server used for continuous integration and delivery. Specifically, the "Job Management" resource with the "List All Jobs" operation allows users to retrieve a list of all jobs configured in a Jenkins instance.

Typical use cases include:

  • Automating monitoring or reporting workflows by fetching all Jenkins jobs.
  • Integrating Jenkins job data into other systems or dashboards.
  • Triggering further actions based on the list of available jobs.

For example, a user might want to fetch all jobs to display their statuses in a custom dashboard or to trigger builds conditionally based on job existence.

Properties

Name Meaning
Job Fields The specific fields to retrieve from each job. This is a string representing a tree query fragment (e.g., [name,color]) that filters which job properties are returned.

Output

The output is a JSON array where each element represents a Jenkins job object containing the requested fields.

  • The structure depends on the Job Fields parameter; it controls which properties of each job are included.
  • For example, if Job Fields is [name,color], each job object will have at least name and color properties.
  • The output does not include binary data for this operation.

Example output snippet:

[
  {
    "name": "ExampleJob1",
    "color": "blue"
  },
  {
    "name": "ExampleJob2",
    "color": "red"
  }
]

Dependencies

  • Requires a Jenkins server URL and an API authentication token or credentials configured in n8n.
  • The node uses HTTP requests authenticated via these credentials to communicate with the Jenkins REST API.
  • No additional external dependencies beyond Jenkins and its API.

Troubleshooting

  • No credentials found: The node throws an error if Jenkins credentials are missing or not configured properly. Ensure you have set up the required API authentication token or username/password in n8n credentials.
  • Invalid Job Fields syntax: If the Job Fields parameter is malformed, the Jenkins API may return an error or incomplete data. Use correct tree query syntax as per Jenkins API documentation.
  • Network or connectivity issues: Failures to connect to the Jenkins server will cause errors. Verify the Jenkins base URL and network accessibility.
  • Permission errors: Insufficient permissions for the API token can result in authorization errors. Make sure the token has read access to job information.

Links and References

Discussion