# Install jenkins-cli with Homebrew, MacPorts, Nix, scoop CLI for jenkins. Version 0.0.47 via Homebrew; verified 2026-07-26. Also installable with macports: sudo port install jenkins-cli. ## Install ```sh sudo av install brew:jenkins-cli ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install jenkins-cli ``` Evidence: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install jenkins-cli ``` Evidence: MacPorts ports tree: devel/jenkins-cli/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - Nix (92%): ```sh nix profile install nixpkgs#jcli ``` Evidence: nixpkgs package indexes: pkgs/by-name/jc/jcli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - Scoop (92%): ```sh scoop install main/jcli ``` Evidence: Scoop official bucket manifest trees: bucket/jcli.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:jenkins-cli - **Package manager:** Homebrew - **Version:** 0.0.47 - **Source summary:** CLI for jenkins - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T04:08:07+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - jcli (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.0.47 ## Project history and usage jenkins-cli in Homebrew is jcli, a Go command-line client from the Jenkins Chinese community for managing Jenkins servers without using the Java jenkins-cli.jar workflow for every command. ### Project history A Jenkins project blog post in 2019 explains the motivation: Jenkins already had a built-in CLI, but the Java invocation was wordy, required a JRE, and was awkward for users expecting a native command. jcli was created as a Go-based CLI that runs natively on common desktop and server platforms. The GitHub repository was created in June 2019 and its early release stream began with v0.0.5 that same month. The README presents the tool as useful for plugin developers, administrators, and regular Jenkins users. ### Adoption history jcli's adoption niche is convenience packaging. The project documentation advertises Homebrew, MacPorts, Linux tarballs, Scoop, and Chocolatey-style installation paths, which turns Jenkins administration into a normal package-manager install instead of a controller-provided jar download. ### How it is used The tool focuses on multiple Jenkins server profiles, plugin listing and installation, job search/build/log operations, Configuration as Code support, browser opening, restart commands, and proxy-aware connections. Its config file stores server URL, username, token, and proxy settings so users can switch between Jenkins instances. ### Why package nerds care This formula matters because it packages a third-party Jenkins client under a name that can be confused with Jenkins' built-in CLI. Package users get a native `jcli` binary, not the upstream Jenkins `jenkins-cli.jar`, so the history helps distinguish the Go client from the automation server's own command interface. ### Timeline - 2019: the jenkins-zh/jenkins-cli repository was created in June. - 2019: v0.0.5 was published on June 22 as an early GitHub release. - 2019: the Jenkins project blog described jcli as a Go-native alternative for managing Jenkins from the command line. ### Related projects - Jenkins' built-in CLI is the direct comparison point and remains distributed by Jenkins controllers as jenkins-cli.jar. - Configuration as Code is a related Jenkins administration workflow supported by jcli commands. - The jenkins-zh documentation and plugin repositories form the surrounding project family for jcli. ### Sources - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ~/.jenkins-cli.yaml ## Credential files - Unix: ~/.jenkins-cli.yaml ## Other Package-Manager Records - MacPorts - jenkins-cli: normalized package name match | MacPorts ports tree: devel/jenkins-cli/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 - Nix - jcli: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/jc/jcli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Scoop - main/jcli: installed executable or alias match | Scoop official bucket manifest trees: bucket/jcli.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/jenkins-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/jenkins-cli.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph