Developer & CI · wired today
Drive Jenkins with governed agents
Build, review and release state is where agents earn their keep. The Jenkins connector is one of 205 executable connectors and gives agents 6 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Jenkins
| Tool | What it does |
|---|---|
get_root | Get Jenkins controller metadata: mode, executor count, security settings and the top-level job list |
list_jobs | List the top-level Jenkins jobs with their URL and last-build colour, without the rest of the controller payload |
get_job | Get one Jenkins job's configuration, health report and last-build pointers by job name |
list_builds | List recent builds of one Jenkins job with their result, timestamp and duration |
whoami | Identify the Jenkins user the stored API token authenticates as |
get_queue | List items waiting in the Jenkins build queue, with the reason each one is still queued |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Jenkins connector needs
You provide username, API token, base URL from your Jenkins account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Jenkins's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Jenkins instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.
Jenkins integration FAQ
What can Quox agents do with Jenkins?
Agents can run 6 read-only tools against Jenkins: get root, list jobs, get job, list builds, whoami and more. Every call is receipted in the evidence trail.
What does the Jenkins integration need?
You provide username, API token, base URL from your Jenkins account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Jenkins credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Jenkins connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Jenkins instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.