Jenkins Community Node icon

Jenkins Community Node

Jenkins Node
Join our community

Actions16

Overview

The node integrates with Jenkins, a popular automation server used for continuous integration and delivery. Specifically, the "Trigger Job Build" operation allows users to start a build process for a specified Jenkins job. This is useful in scenarios where automated workflows need to initiate Jenkins jobs as part of deployment pipelines, testing sequences, or other CI/CD tasks.

For example, after code is pushed to a repository, an n8n workflow can trigger a Jenkins job to run tests or deploy the application automatically. This node operation simplifies integrating Jenkins build triggers into broader automation workflows without manual intervention.

Properties

Name Meaning
Job Name The exact name of the Jenkins job you want to trigger a build for. This is a required string input.

Output

The output JSON contains a simple status confirmation indicating whether the build trigger request was successful. It looks like this:

{
  "status": "success"
}

No detailed build information or logs are returned by this operation directly. The node confirms that the HTTP POST request to trigger the build was accepted by Jenkins.

Dependencies

  • Requires a 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: If the node throws an error about missing credentials, ensure that valid Jenkins API credentials are configured in n8n and selected in the node.
  • Job not found or invalid job name: If the job name does not exist on the Jenkins server, the build trigger will fail. Verify the job name spelling and existence.
  • Permission issues: The Jenkins user associated with the API token must have permission to trigger builds on the specified job.
  • Network connectivity: Ensure n8n can reach the Jenkins server URL; network issues or firewalls may block access.
  • Unexpected HTTP errors: Check Jenkins server logs and API documentation for specific error codes if the build trigger fails.

Links and References

Discussion