Jenkins
Developer ToolsManage Jenkins jobs, trigger and monitor builds, inspect the build queue, and query system information from your flows over the Jenkins remote access API.
What This Integration Enables
FlowRunner agents use Jenkins to run CI/CD from inside a larger flow instead of from the Jenkins UI. An agent can trigger a build with parameters and follow it to completion, create, copy, enable, disable, or delete jobs, and capture build results and console output for reporting, alerting, or archiving. It can monitor the build queue and cancel stuck or unwanted queued builds, and pull version, mode, and view information for dashboards and health checks. Because Jenkins queues rather than runs immediately, the agent tracks a build from its queue item into execution. What it does not do on its own is trigger the job that ships to production. That trigger waits for the engineer who owns the deploy.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Build on change with a production deploy gate
A push arrives. The agent calls Trigger Build for the matching job, follows the queue item into execution with Get Queue and Get Build, and posts the build status back onto the pull request. When the build is green and a deploy job is next, the agent does not run it. It asks an engineer to approve the production deploy, and only after the approval does it call Trigger Build on the deploy job. Tests run automatically; the ship stays a decision.
Failure to a page
After Get Build reports a failed result, the agent pulls the console log with Get Build Console Output and opens an incident in the on-call tool, attaching the failing job and the log. A red build reaches the on-call engineer with the output already gathered.
Job lifecycle from a flow
When a new service repository is created, the agent calls Copy Job from a template job to stand up its build, then Enable Job. When a service is retired, it calls Disable Job. Build configuration keeps pace with the services without an engineer clicking through the UI.
Human-in-Loop Highlight
The human-in-loop moment in Jenkins is the production deploy gate. Triggering test builds, following the queue, and reading console output are all safe to automate, so the agent runs them by rule. Triggering the job that deploys to production is not, so the agent stops. When a build is green and a deploy job is next in the flow, the agent posts the build result to the deploys channel and asks: "my-app-build #217 passed on main. Trigger the deploy-prod job?" A named engineer approves. Only then does the agent call Trigger Build on the deploy job. The agent runs CI on its own. A person owns the deploy to production.
Agent Capabilities
17 actionsJobs
8- Copy Job Create a job by copying an existing one. Used to stand up a build from a template.
- Create Job Create a job from a config XML.
- Delete Job Delete a job.
- Disable Job Disable a job so it stops accepting builds.
- Enable Job Re-enable a disabled job.
- Get Job Retrieve a job's details, including its last build.
- Get Job Config Retrieve a job's config XML.
- List Jobs List the jobs on the instance.
Builds
5- Get Build Retrieve a build's details and result.
- Get Build Console Output Retrieve a build's full console log. Used to attach failure output to an alert.
- Get Build Log Tail Retrieve the tail of a build's console log.
- Stop Build Stop a running build.
- Trigger Build Queue a build, with parameters if the job takes them. Returns the queue item, not the build number. Run it behind a human gate when it deploys to production.
Queue
2- Cancel Queue Item Cancel a queued build before it starts.
- Get Queue Retrieve the build queue. Used to follow a build from queue into execution.
System
2- Get Jenkins Info Retrieve the instance version, mode, and view information.
- Get Views List the views configured on the instance.
Start building with Jenkins
$100 in credits. No card required. Connect in minutes.