Integration · Developer
AI agents for Jenkins
Run and watch Jenkins jobs on your own Jenkins server.
- Actions
- 8
- Read
- 7
- Write
- 1
Actions
What your agents can do in Jenkins
Run and watch Jenkins jobs on your own Jenkins server: list jobs and folders, read a job's recent builds and parameters, start a build with parameters, follow it from the queue, read its result, changes and console log, and see the build queue and agents, as a user with an API token.
Read 7
Look things up. Nothing changes.
List jobs
Lists the jobs at the top of Jenkins, or inside one folder, as jobs.
Get a job
Reads one job: description, color, buildable, inQueue, its last build, last successful and last failed build, the 10 most recent builds.
Get a queued build
Reads a queue item from start_build: why it is waiting, blocked, cancelled, and executable (the build's number and url) once it has started.
Get a build
Reads one build of a job: result (SUCCESS, FAILURE, UNSTABLE, ABORTED, NOT_BUILT; null while building), duration and estimatedDuration (ms), timestamp.
Read a build's console log
Returns a build's console output as text in result, from byte start to the end (from the beginning by default).
List the build queue
Lists the builds waiting to run, as items: each with id, task (the job's name and url), why it waits, blocked, stuck and inQueueSince (epoch ms).
List build agents
Lists the controller and its agents (nodes), as computer: each with displayName, offline, temporarilyOffline, offlineCauseReason, idle and numExecutors.
Write 1
Create, change or send.
Start a build
Queues a build of a job.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the API credentials from your Jenkins account.
What you enter
- User name
- API token
Settings
- Jenkins address
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Jenkins data
Ask a question in plain words. The agent can list jobs, get a job or get a queued build in Jenkins, then answers with what it found.
- 02
Let an agent update Jenkins
Have the agent start a build in Jenkins as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Jenkins and Slack: it can list jobs in Jenkins and post a summary to a Slack channel in the same run.
FAQ
Jenkins and MyDeepAgents
Can MyDeepAgents connect to Jenkins?
Yes. The Jenkins connector has 8 actions: 7 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Jenkins?
Enter the API credentials from your Jenkins account. You'll need: User name and API token. The connection also asks for: Jenkins address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Jenkins without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use Jenkins in workflows as well as agents?
Yes. Every Jenkins action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Jenkins to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.