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 Build Management resource with the List Build Artifacts operation allows users to retrieve metadata about artifacts produced by a specific build of a Jenkins job.

Typical use cases include:

  • Automating retrieval of build artifact information after a Jenkins job completes.
  • Integrating Jenkins build outputs into downstream workflows, such as deployment pipelines or quality checks.
  • Monitoring and auditing build artifacts programmatically.

For example, after triggering a build in Jenkins, you can use this node to list all artifacts generated by that build, enabling automated download or further processing.

Properties

Name Meaning
Job Name The name of the Jenkins job whose build artifacts you want to list.
Build Number The specific build number of the job to query for artifacts (e.g., "1", "42").

Output

The output is a JSON array containing the details of the build artifacts associated with the specified job and build number. Each item typically includes artifact metadata such as file names and relative paths.

Example output structure (simplified):

[
  {
    "artifacts": [
      {
        "fileName": "example-artifact.jar",
        "relativePath": "target/example-artifact.jar"
      },
      {
        "fileName": "report.html",
        "relativePath": "reports/report.html"
      }
    ]
  }
]

No binary data is returned by this operation; it only provides metadata about the artifacts.

Dependencies

  • Requires an active Jenkins server accessible via its 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 endpoints.

Troubleshooting

  • No credentials found: Ensure that Jenkins API credentials are properly set up in n8n and linked to the node.
  • Invalid Job Name or Build Number: Verify that the job name and build number exist on the Jenkins server. Typos or non-existent builds will cause errors or empty results.
  • Network issues: Confirm that the Jenkins server URL is reachable from the n8n environment.
  • Permission denied: The API user must have permission to access job and build information on Jenkins.
  • Unexpected response format: If Jenkins is customized or uses plugins altering API responses, the node might not parse artifact data correctly.

Links and References

Discussion