Jenkins Community Node

Overview

This node integrates with Jenkins, a popular automation server used for continuous integration and delivery. Specifically, the "Trigger Job Build with Parameters" operation allows users to start a Jenkins job build while passing custom parameters to it. This is useful when you want to trigger builds dynamically with different configurations or inputs without manually starting them in Jenkins.

Common scenarios include:

• Automating deployment pipelines where each build requires specific environment variables or version numbers.
• Running parameterized tests by triggering jobs with different test suites or settings.
• Integrating Jenkins builds into larger workflows that require dynamic input values.

Example: Triggering a Jenkins job named "DeployApp" with parameters like environment=production and version=1.2.3 to deploy a specific app version to production.

Properties

Name	Meaning
Job Name	The exact name of the Jenkins job to trigger.
Parameters	A collection of key-value pairs representing the parameters to pass to the job build.

The Parameters property supports multiple entries, each requiring:

• Name: The parameter's name as defined in the Jenkins job configuration.
• Value: The value to assign to that parameter for this build.

Output

The output JSON contains a simple status confirmation indicating whether the build trigger request was successful. For example:

{
  "status": "success"
}

No detailed build information or logs are returned immediately since the build runs asynchronously on Jenkins.

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 with proper authentication headers to communicate with Jenkins REST API endpoints.

Troubleshooting

• No credentials found: Ensure that valid Jenkins API credentials are configured in n8n before running the node.
• Job not found or invalid job name: Verify the job name exactly matches the one configured in Jenkins.
• Parameter mismatch errors: Confirm that all parameter names correspond to those defined in the Jenkins job and that required parameters are provided.
• HTTP errors (e.g., 403, 404): Check Jenkins server accessibility, user permissions, and correct API endpoint URLs.
• Content-Type header issues: The node sets application/x-www-form-urlencoded for parameterized builds; ensure Jenkins accepts this content type.

Links and References

• Jenkins REST API Documentation
• Jenkins Parameterized Builds
• n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)