Integrations/Jenkins

Control what your AI agents do in Jenkins.

Let your team build AI agents for Jenkins. Bollard AI controls what each one can do, job by job.

Request early accessSee how it works →
Jenkins
Release Agent
build-web JobOffReadFull use
build-api JobOffReadFull use
deploy-prod JobOffReadFull use
Delete jobs
What agents can do

Set what each agent can do in every job.

Each job gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see the job or that it exists.
Read
Read-only
The agent can read builds and history for that job. It can't change anything.
Full use
Run and update
The agent can trigger and update that job.

Some actions stay off until explicitly turned on

Each one removes build history for good or changes how Jenkins itself runs, so it could override the limits set on individual jobs.

Deleting jobs and build historyCancelling queued buildsChanging system and plugins
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's Jenkins a single time and chooses which jobs it covers. Any job left out stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, trigger, and update a single job
Example

A build release agent.

A release agent triggers build-web and can read build-api, but it can't open deploy-prod or delete a job.

build-web JobOffReadFull use
build-api JobOffReadFull use
deploy-prod JobOffReadFull use

Manage access

ALLOWEDRelease Agent triggered build-web
ALLOWEDRelease Agent read a build in build-api
BLOCKEDRelease Agent tried to open deploy-prod, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and Jenkins, so they never hold your Jenkins keys and never reach Jenkins directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to Jenkins. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every job starts off-limits, and deleting build history is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your Jenkins keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which job or build, and the decision. The record is readable and can't be edited after the fact.

Questions

Jenkins, answered.

Does connecting Jenkins hand Bollard AI all your jobs?+
Only what's connected. An admin chooses which jobs Bollard AI covers, and that sets the most any agent could reach. Bollard AI doesn't browse or copy your build setup. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent delete jobs or change Jenkins itself?+
Not unless you turn it on. Deleting jobs and build history, and changing the system and plugins, are held off by default, so an agent can trigger and read builds where you allow without ever removing history or reconfiguring Jenkins, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our Jenkins keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches Jenkins, and the blocked attempt lands in the activity record with the reason.
How do we connect Jenkins?+
An admin connects the company's Jenkins once. Bollard AI seals the connection and builds the list of jobs to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in Jenkins, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →