Start free
ActionJenkinsUpdated June 2026

How do I fetch a Jenkins build's console output?

Short answer: You can get jenkins build log in Jenkins by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jenkins Get Jenkins Build Log action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Jenkins Build Log in Jenkins — start free All 4 Jenkins actions
Get Jenkins Build Log in Jenkins — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Job Name
job_name
stringRequiredJob Name
Build Number
build_number
stringRequiredBuild 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.

Triggered by

Apps that pair well as the trigger for Get Jenkins Build Log.

Any of these apps can fire this action as part of a workflow.

Gmail → Jenkins
1 Gmail triggers
Slack → Jenkins
13 Slack triggers
Google Sheets → Jenkins
2 Google Sheets triggers
HubSpot → Jenkins
18 HubSpot triggers
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. TinyCommand handles Jenkins's rate limits automatically so you don't have to throttle manually.
More actions

Other Jenkins actions.

Action
Get Jenkins Build Status
Returns the current state of a specific build number — queued, building, success, failure, aborted. The standard polling lookup after Trigger Build.
Action
List Jenkins Jobs
Returns every job visible on the Jenkins instance organised by folder. Useful for resolving job paths at workflow setup or for inventorying the CI configuration.
Action
Trigger Jenkins Build
Starts a job optionally with parameters. Returns a queue item ID; the actual build number assigns when the queue dequeues. For "Linear issue moved to staging → trigger deploy job" or "external event → CI run" workflows.
Get Jenkins Build Log in Jenkins — start free