Jenkins
Trigger builds, inspect jobs, and manage the build queue on any Jenkins instance.
About
Jenkins ships in the w6w first-party pack. It declares 6 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.jenkins- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- DevOps & Infrastructure
Overview
Jenkins connects a workflow to any Jenkins instance — a customer’s own CI box, an on-prem network segment, or a managed offering — to trigger builds, inspect jobs, manage the build queue and stop a build in progress. Because Jenkins is almost always self-hosted, the instance’s own base URL is collected on the connection rather than pinned to a single vendor host, and every action builds its request against that URL.
Triggering a build queues it rather than starting it immediately; the useful part of the response is a queue item, which a separate action resolves once Jenkins actually schedules an executor and hands back the real build number. Job names accept a folder path, so builds inside a Folders-plugin or multibranch-pipeline layout are addressed the same way a flat job would be.
Build with Jenkins
Three routes to the same 6 actions. The Workflow tab is generated from Jenkins's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Build Status
get-build-status Get the status/result of a specific build, or a permalink such as `lastBuild`.
Get Job Info
get-job-info Get a job's configuration model — buildability, status color, next build number.
Get Queue Item
get-queue-item Get the status of a queued build — its wait reason, or the build it resolved to.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Jenkins's real ids.
{
"manifestVersion": "2",
"name": "jenkins-example",
"steps": [
{
"id": "get-build-status",
"uses": {
"app": "io.w6w.jenkins",
"action": "get-build-status",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"job": "<job>"
}
}
]
}Here are some of the things you can do
-
Get Build Status
readget-build-status -
Get Job Info
readget-job-info -
Get Queue Item
readget-queue-item -
List Jobs
readlist-jobs -
Stop Build
performstop-build
+1 more action available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Jenkins, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Jenkins. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "trigger-build",
payload: {
job: "<value>",
// parameters: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action trigger-build --payload '{"job":"<value>"}'Give an AI agent Jenkins — without giving it Jenkins's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.jenkins#get-build-status",
"input": {
"job": "<job>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Jenkins connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Jenkins's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Jenkins itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Jenkins declares its own checks, so its health is a property of the app rather than something the host guesses at.
Jenkins platform status
Instance reachable
Unauthenticated `GET /api/json` against this connection's endpoint. A 401/403 counts as reachable — it proves a live Jenkins instance evaluated and rejected the anonymous request.