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
- In Jenkins, create an API token for your user.
- Open the agent → Toolkits → add Jenkins.
- Create a connection with Jenkins URL, username, and API token.
- Save the agent.
@-mention Jenkins tools for CI tasks.
Jobs & builds
| Tool | Description |
|---|
| Validate Credentials | Validates Jenkins credentials. |
| List Jobs | Lists jobs. |
| Get Job | Returns job details. |
| Create Job | Creates a job. |
| Delete Job | Deletes a job. |
| Copy Job | Copies a job. |
| Get Build | Returns build details. |
| Trigger Build | Triggers a build. |
| Get Build Log | Returns build console output. |
| Stop Build | Stops a running build. |
Nodes, queue & pipelines
| Tool | Description |
|---|
| List Nodes | Lists nodes/agents. |
| Get Node | Returns node details. |
| Get Queue | Returns the build queue. |
| List Pipelines | Lists pipelines. |
| Get Pipeline Run | Returns a pipeline run. |
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
| Symptom | What to check |
|---|
| Auth failed | URL, username, and API token; CSRF crumb settings if applicable |
| Job not found | Exact job path/name and folder structure |
| Cannot trigger build | Job permissions and whether the job is parameterized |