# Install jenkins with Homebrew, apk, chocolatey, MacPorts, Nix, pacman, scoop

Extendable open source continuous integration server. Version 2.572 via Homebrew; verified 2026-07-07.

## Install

```sh
sudo av install brew:jenkins
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install jenkins
```

  Evidence: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install jenkins
```

  Evidence: MacPorts ports tree: devel/jenkins/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- apk (92%):

```sh
sudo apk add jenkins
```

  Evidence: Alpine Linux edge package indexes: jenkins from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

- Nix (92%):

```sh
nix profile install nixpkgs#jenkins
```

  Evidence: nixpkgs package indexes: pkgs/by-name/je/jenkins/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S jenkins
```

  Evidence: Arch Linux sync databases: jenkins from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

### Windows

- Chocolatey (92%):

```sh
choco install jenkins
```

  Evidence: Chocolatey community package catalog: jenkins from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','invantive-control-for-excel'

- Scoop (92%):

```sh
scoop install main/jenkins
```

  Evidence: Scoop official bucket manifest trees: bucket/jenkins.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:jenkins
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/jenkins>
- **Version:** 2.572
- **Source summary:** Extendable open source continuous integration server
- **Homepage:** <https://www.jenkins.io/>
- **Repository:** <https://github.com/jenkinsci/jenkins>
- **Upstream docs:** <https://www.jenkins.io/doc>
- **License:** MIT
- **Source archive:** <https://get.jenkins.io/war/2.572/jenkins.war>
- **Last updated:** 2026-07-07T09:59:02Z
- **Generated:** 2026-07-08T07:18:31+00:00

## Executables

- jenkins (cli)
- jenkins-cli (cli)
- jenkins (alias)
- jenkins-cli (alias)

## Dependencies

- openjdk@21

## Install behavior

- Post-install hook: not defined
- Service: declared
- Caveats: Note: When using launchctl the port will be 8080.
- Bottle: available on all

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 2.572
- Package-manager updated: 2026-07-07
- Local data: ok
- Upstream repository: https://www.jenkins.io/
- info: Release/tag comparison is only available for GitHub repositories.
## Project history and usage

Jenkins is an open-source automation server used for continuous integration, delivery, and deployment workflows. In package-manager form it is a service-oriented Java application plus command-line entry points rather than a small single-purpose CLI.

### Project history

The project began as Hudson in 2004, created by Kohsuke Kawaguchi while he worked at Sun Microsystems. The origin story preserved by the Jenkins community describes Hudson as a way to test code before commits so broken builds would not surprise a team.

In January 2011, Hudson community leaders proposed renaming the project to Jenkins after talks with Oracle left unresolved control over the Hudson name. The follow-up vote produced a strong result for renaming, and the project began moving domains, mailing lists, and GitHub organization identity to Jenkins.

Jenkins developed as an extensible automation server with a large plugin ecosystem, a web administration model, Pipeline-as-code workflows, agents, remoting, and CLI/API surfaces. That breadth explains why package managers often split Jenkins into regular and LTS formulas.

### Adoption history

Jenkins spread through development and operations teams because it combined a self-hosted automation server with plugins and job configuration that could fit many build systems, source-control hosts, test runners, artifact stores, and deployment workflows.

The project documentation treats the CLI, plugins, Pipeline, and LTS release line as ordinary administration surfaces, showing how Jenkins adoption includes both interactive web use and scripted operations.

### How it is used

Package users install Jenkins to run a controller service, manage jobs and plugins, expose web and API endpoints, and interact with the server through the bundled CLI. Jenkins stores much of its controller and job configuration under JENKINS_HOME as XML files, while newer workflows often define build logic in Jenkinsfiles through Pipeline.

### Why package nerds care

Jenkins is package-nerd significant because it is an application, service, plugin host, Java runtime workload, and CLI endpoint all at once. A formula has to encode service startup, upgrade behavior, filesystem state, and compatibility expectations, not merely place a binary on PATH.

The separate Jenkins and Jenkins LTS formulas are also a useful packaging example: the package name communicates release cadence and operational posture while both formulas point back to the same upstream project.

### Timeline

- 2004: Hudson, later Jenkins, was started by Kohsuke Kawaguchi at Sun Microsystems.
- 2010: the jenkinsci/jenkins GitHub repository was created in November.
- 2011: Hudson community leaders proposed the Jenkins rename in January.
- 2011: the rename vote concluded with 214 eligible votes for renaming and 14 for the status quo.
- 2011: Jenkins infrastructure began moving domains, groups, and GitHub organization naming to the Jenkins identity.

### Related projects

- Hudson is the predecessor name and historical fork context for Jenkins.
- Jenkins Pipeline is the related workflow system for defining delivery logic as code.
- Jenkins plugins are the integration mechanism that connects the server to source control, build tools, cloud providers, credentials, notifications, and deployment systems.
- Jenkins LTS is the related conservative release line packaged separately by Homebrew.

### Sources

- <https://community.jenkins.io/t/lets-thank-kohsuke-the-creator-of-jenkins/168>
- <https://github.com/jenkinsci/jenkins>
- <https://www.jenkins.io/blog/2011/01/11/hudsons-future/>
- <https://www.jenkins.io/blog/2011/01/29/jenkins/>
- <https://www.jenkins.io/doc/book/managing/cli/>
- <https://www.jenkins.io/doc/book/managing/plugins/>
- <https://www.jenkins.io/doc/book/pipeline/>


## Security Notes

formula declares a Homebrew service.

- **Geiger risk:** orange / medium
- formula declares a Homebrew service


## 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_HOME/config.xml, $JENKINS_HOME/*.xml, $JENKINS_HOME/jobs/[JOBNAME]/config.xml
## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** jenkins
- **Aliases:** hudson
- **Version Scheme:** 0
- **Revision:** 0
- **Head Version:** HEAD
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** head, stable

## Other Package-Manager Records

- Nix - jenkins: normalized package name match | nixpkgs package indexes: pkgs/by-name/je/jenkins/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- apk - jenkins - 2.555.1-r0: normalized package name match | Alpine Linux edge package indexes: jenkins from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Extendable continuous integration server (LTS version) | https://jenkins.io/
- apk - jenkins-openrc - 2.555.1-r0: normalized package name match | Alpine Linux edge package indexes: jenkins-openrc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Extendable continuous integration server (LTS version) (OpenRC init scripts) | https://jenkins.io/
- pacman - jenkins - 2.567-1: normalized package name match | Arch Linux sync databases: jenkins from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Extendable continuous integration server (latest) | https://jenkins.io
- MacPorts - jenkins: normalized package name match | MacPorts ports tree: devel/jenkins/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - jenkins: normalized package name match | Chocolatey community package catalog: jenkins from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','invantive-control-for-excel'
- Scoop - main/jenkins: normalized package name match | Scoop official bucket manifest trees: bucket/jenkins.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- MacPorts - jenkins-cli: installed executable or alias match | MacPorts ports tree: devel/jenkins-cli/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Related links

- [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals.
- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata.
- [openjdk@21](https://www.automicvault.com/pkg/brew/openjdk-21/) - Runtime dependency declared by Homebrew.
- [jenkins-cli](https://www.automicvault.com/pkg/brew/jenkins-cli/) - Package name indicates the same formula family.
- [jenkins-lts](https://www.automicvault.com/pkg/brew/jenkins-lts/) - Shares the same upstream homepage.
- [act](https://www.automicvault.com/pkg/brew/act/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools, devops.
- [jenkins-job-builder](https://www.automicvault.com/pkg/brew/jenkins-job-builder/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools, jenkins.
- [woodpecker-cli](https://www.automicvault.com/pkg/brew/woodpecker-cli/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools, devops.
- [brigade-cli](https://www.automicvault.com/pkg/brew/brigade-cli/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools.
- [circleci](https://www.automicvault.com/pkg/brew/circleci/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools.
- [dagger](https://www.automicvault.com/pkg/brew/dagger/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools.

## Combined YAML source

View the package source record on GitHub. [combined/jenkins.yml](https://github.com/automic-vault/db/blob/main/combined/jenkins.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
