Jenkins CLI

Read-only build visibility for Jenkins via af jenkins. Eight subcommands — jobs, job, branches, build, log, queue, stages, stage-log. Nothing here triggers, cancels, or mutates a build.

Setup

Jenkins uses its own credentials — Atlassian, Bitbucket, and Sonar tokens are not interchangeable. All three variables are required; there are no fallbacks, no CLI flags, and no af.json block for Jenkins.

Add to your project's .env:

• JENKINS_BASE_URL — Jenkins instance URL (e.g. https://jenkins.example.com; a trailing slash is stripped)
• JENKINS_USER — Your Jenkins username
• JENKINS_API_TOKEN — API token from <jenkins>/user/<you>/configure

They are combined as HTTP Basic auth. Config is read lazily on the first API call, so a missing variable surfaces as a runtime error (JENKINS_USER is not set. Create a .env file in your project directory with: ..., exit 1), not as a startup error.

Run af jenkins from the repo root that holds the .env. af auto-loads .env from the current working directory only, and it never overwrites variables already set in the environment.

Job Paths