Get Jenkins Build Log: 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
Build Number build_number	string	Required	Build Number. Example: 42 or lastBuild

Sample request

{
  "job_name": "{{trigger.job_name}}",
  "build_number": "e.g. 42 or lastBuild"
}

Returns

{
  "url": "https://jenkins.example.com/job/my-project/42/",
  "result": "SUCCESS",
  "building": false,
  "duration": 45000,
  "timestamp": 1712835600000,
  "displayName": "#42"
}

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

FAQ

Questions about Get Jenkins Build Log.

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

Returns the full stdout/stderr of the build as plain text. For "post error log to Slack on deploy failure" diagnostic workflows. For very long logs, use the progressiveText endpoint via HTTP action for streaming.

What inputs does Get Jenkins Build Log require?

Required: Job Name, Build Number. 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 Log support batch operations?

Yes. Run Get Jenkins Build Log 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