Get Jenkins Build Status: Jenkins action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Job Name job_name	string	Required	Job Name. Example: my-pipeline
Build Number build_number	string	Optional	Specific build number, or leave empty for last build

Sample request

{
  "job_name": "e.g. my-pipeline",
  "build_number": "e.g. 42 or lastBuild"
}

Returns

{
  "url": "https://jenkins.example.com/job/my-pipeline/42/",
  "number": 42,
  "result": "SUCCESS",
  "building": false,
  "duration": 120000,
  "timestamp": 1700000000000
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Jenkins Build Status.

What does the Get Jenkins Build Status action do in Jenkins?

Returns the current state of a specific build number — queued, building, success, failure, aborted. The standard polling lookup after Trigger Build.

What inputs does Get Jenkins Build Status require?

Required: Job Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Jenkins returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Jenkins Build Status support batch operations?

Yes. Run Get Jenkins Build Status inside a Loop node to process arrays. Tiny Command handles Jenkins's rate limits automatically so you don't have to throttle manually.

More actions