Jenkins has evolved.

Run Jenkinsfiles the way GitHub Actions runs workflows, with no Jenkins server to run, back up, or restart. Or run a classic Jenkins that is yours alone.

What Varroa runs

Drive the fleet with an AI agent

One agent session: it stands up a Jenkins, runs a job, and reads the result.

Bring up a Jenkins controller for team-alpha and run its smoke-test job.
create_composed_bundle({ name: "team-alpha-baseline", inputs: [...] })
→ ComposedBundle/team-alpha-baseline ready, contentRef resolved
create_controller({ name: "team-alpha", namespace: "teams-platform", composedBundleRef: "team-alpha-baseline" })
→ Controller/team-alpha created, phase: Provisioning
call_jenkins_tool({ name: "team-alpha", method: "tools/call", params: { name: "build_job", … } })
→ Build #1 queued, then SUCCESS
call_jenkins_tool({ name: "team-alpha", method: "tools/call", params: { name: "get_build_log", … } })
→ "smoke-test PASSED"

Example session. Tool names and arguments are real; the responses are illustrative.

The fleet overview: the phase of every controller, the controllers that need a look, and recent activity in one place. Tap to expand.

Already running CloudBees CI?

See how Varroa's CRD-native controllers, bundles, and RBAC federation line up against CloudBees CI, and what changes if you migrate.

Compare Varroa to CloudBees CI