Skip to main content
The Jenkins toolkit lets agents list and manage jobs, trigger and inspect builds, read build logs, work with nodes and the queue, and inspect pipelines. Authentication uses Jenkins URL, username, and API token (HTTP Basic) saved as a connection. Add it on the agent Toolkits tab and create or select a Jenkins connection.

​
Prerequisites

  • A Jenkins URL reachable from the platform
  • A Jenkins user and API token with permissions for the jobs the agent should use
  • An agent you can edit

​
Setup

  1. In Jenkins, create an API token for your user.
  2. Open the agent → Toolkits → add Jenkins.
  3. Create a connection with Jenkins URL, username, and API token.
  4. Save the agent. @-mention Jenkins tools for CI tasks.

​
Available tools

​
Jobs & builds

​
Nodes, queue & pipelines

​
Use cases

  • Trigger a build and poll status from chat
  • Summarize the latest failing build log
  • List jobs or queue depth during an incident

​
Tips

  • Prefer a least-privilege Jenkins user and token.
  • Confirm destructive actions (Delete Job, Stop Build) with the user first.
  • Store the API token in a saved connection — do not put it in the personality prompt.

​
Troubleshooting