Skip to main content

zenkins

CLI tool for Jenkins. List jobs, check builds, view logs, trigger builds.

Install

uv tool install zenkins

Setup

Run zenkins init to get started. If no config file exists, it creates one with placeholder values:

url = "http://your-jenkins.example.com"
user = "your-username"
token = "your-api-token"

The config file location depends on your OS:

OS Path
Linux ~/.config/zenkins/config.toml
macOS ~/Library/Application Support/zenkins/config.toml
Windows %APPDATA%\zenkins\config.toml

Edit the file with your Jenkins URL, username, and API token, then run zenkins init again to verify connectivity.

Creating an API token

  1. Log in to your Jenkins instance
  2. Click your username (top right) → Configure
  3. Scroll to API TokenAdd new Token
  4. Give it a name, click Generate, and copy the token

The token is shown only once — paste it into config.toml right away.

Usage

zenkins jobs                        # List all jobs with status
zenkins status <job>                # Show last build info
zenkins builds <job>                # List recent builds
zenkins builds <job> -n 5           # List last 5 builds
zenkins log <job>                   # Show console output (last build)
zenkins log <job> 42                # Show console output for build #42
zenkins queue                       # Show build queue
zenkins build <job>                 # Trigger a build
zenkins failures <job>              # Show failing tests (last build)
zenkins failures <job> 42           # Show failing tests for build #42
zenkins failures <job> 40..45       # Failure summary across build range
zenkins failures <job> -n 10        # Failure summary for last 10 builds
zenkins artifacts <job> -l          # List artifacts (last build)
zenkins artifacts <job> 42 -d ./out # Download artifacts to directory
zenkins artifacts <job> --glob "*.xml" # Download matching artifacts
zenkins artifacts <job> -n 3 --glob "*.png" -l  # List PNGs from last 3 builds

Folder jobs use / syntax: zenkins builds ci/main, zenkins failures ci/main -n 5.

The failures command queries both JUnit/NUnit and Robot Framework test results, grouping them into persistent, intermittent, and one-off failures when using range or -n syntax.

Library usage

import zenkins

s = zenkins.client()
resp = s.get("http://jenkins.example.com/api/json")

License

MIT

Release files for zenkins 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zenkins 0.5.0
File Size Uploaded
zenkins-0.5.0.tar.gz 15.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for zenkins 0.5.0
File Interpreter ABI Platform
zenkins-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 33.4 kB

Release files / zenkins-0.5.0.tar.gz

Download URL zenkins-0.5.0.tar.gz
Size 15.7 kB
Tags Source
SHA-256 checksum
How to use checksums
cadff4a6b51878a733fde2c57f602cc17832618116ac450ac3d0079f82c13323
BLAKE2b-256 checksum
How to use checksums
e6b9db3c674ec3e50010992ed87295ae8e733de3e684c2e617612f5ed8efde97
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release files / zenkins-0.5.0-py3-none-any.whl

Download URL zenkins-0.5.0-py3-none-any.whl
Size 17.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d6cf66f1d71f1312519ebef44c2076828d2247677be819429fba73f556a04f8c
BLAKE2b-256 checksum
How to use checksums
91af1368d506ce3f14224ddfebff88d41ddbd05457a276e5b1b1960ab1a6aba9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.0 This release

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page