Jenkins Builds & Results connector.

Look up Jenkins jobs, submit builds with optional scalar parameters, track queued builds, and retrieve build results and published JUnit test counts.

Download connector See all connectors

Connector download

Download Jenkins Builds & Results

Versioned ZIP for your CXFabric tenant.

Register the ZIP in your tenant, or add a new version if the connector is already installed.
Create or select a credential if the action requires one.
In a Draft flow, add an available action, choose its version, connect it, and map inputs.
Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Included in this version

Implemented in v0.1.0.0. Use a separate flow trigger; no webhook trigger is included.

Read one bounded page of jobs at the controller root or a folder.

Read job buildability and latest build references.

Verify buildability and submit one build; return its queue ID without polling or retrying.

Track a queue ID and retrieve its build number when execution starts.

Retrieve running or completed build status and timing without console output.

Retrieve total, failed, skipped and derived passed counts from a published JUnit report.

Vendor API

Implementation considerations

Supported scope: Look up Jenkins jobs, submit a build with optional scalar parameters, track its queue entry, and retrieve build results and published JUnit counts.
Select a Basic Auth credential with the Jenkins username and API token in its password field. Set the trusted HTTPS controller URL, including any context path. Lookups require read permissions; build submission also requires Job/Build. The executor must reach the controller and trust its certificate.
Six focused actions. Trigger Build requires explicit confirmation; parameterized jobs use buildWithParameters even when relying on default values. An accepted queue entry is not a completed build. Poll queue and build state in separate invocations. JUnit counts require a published report; unavailable reports return errors, not zero failures.
Requests have a 1–8 second total budget and 1 MiB JSON response limit. No automatic retries, redirects, administration, console logs or artifact downloads. Inspect Jenkins before repeating a submission with an unknown outcome. Local tests and package checks passed; tenant import and live Jenkins execution remain untested.
Unmodified Jenkins logo attributed to the Jenkins project; artwork is licensed under CC BY-SA 3.0. See https://www.jenkins.io/artwork/ and https://creativecommons.org/licenses/by-sa/3.0/.

Support

Tell us what you need to connect or change.