# Install jenkins-lts with Homebrew, scoop Extendable open source continuous integration server. Version 2.555.3 via Homebrew; verified 2026-06-26. ## Install ```sh sudo av install brew:jenkins-lts ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install jenkins-lts ``` Evidence: local Homebrew formula metadata ### Windows - Scoop (92%): ```sh scoop install main/jenkins-lts ``` Evidence: Scoop official bucket manifest trees: bucket/jenkins-lts.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:jenkins-lts - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.555.3 - **Source summary:** Extendable open source continuous integration server - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Last updated:** 2026-06-26T18:36:44+01:00 - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - jenkins-lts (cli) - jenkins-lts-cli (cli) - jenkins-lts (alias) - jenkins-lts-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.555.3 - Package-manager updated: 2026-06-26 - Local data: ok - Upstream repository: https://www.jenkins.io/ - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage Jenkins LTS is the long-term-support packaging track for the Jenkins automation server. It packages the same upstream Jenkins project as the regular Jenkins formula but follows the project's conservative release-line model. ### Project history Jenkins traces its project lineage to Hudson, started in 2004 by Kohsuke Kawaguchi at Sun Microsystems. In January 2011, the Hudson community proposed renaming the project to Jenkins after unresolved trademark and governance concerns with Oracle, and a community vote approved the rename. The Jenkins project then moved infrastructure and identity to the Jenkins name while continuing the automation-server codebase and community. The LTS line was established for users who prefer a slower-moving release stream with selected backports instead of the faster weekly line. ### Adoption history The LTS line addresses conservative production users and companies that stabilize Jenkins internally. The Jenkins LTS documentation describes a 12-week baseline selection cycle, backported bug and security fixes, and three minor releases per baseline on four-week cycles. ### How it is used Homebrew's jenkins-lts formula is for users who want the automation server and CLI wrappers tied to the stable line rather than the weekly line. Administrators still manage Jenkins through JENKINS_HOME XML configuration, plugins, Pipeline jobs, the web UI, and CLI/API tooling. ### Why package nerds care The LTS formula is significant because it encodes a release-policy choice in the package name. Package managers often expose both fast and conservative upstream streams, and Jenkins is a clear example where the same upstream repo yields separate installable formulas for different operational risk profiles. ### Timeline - 2004: Hudson, the project that became Jenkins, was started by Kohsuke Kawaguchi at Sun Microsystems. - 2011: the community proposed the Jenkins rename in January. - 2011: the rename vote concluded with Jenkins as the community project name. - 2011: Jenkins infrastructure such as domains, groups, and GitHub organization names moved toward Jenkins branding. - LTS cycle: baselines are selected every 12 weeks and receive three minor releases on four-week cycles. ### Related projects - brew:jenkins packages the same upstream automation server on the regular release line. - Jenkins plugins, Pipeline, Remoting, and Configuration as Code are central parts of the ecosystem that make the server extensible. - Hudson is the predecessor name and historical fork context for Jenkins. ### Sources - - - - - ## 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-lts - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Scoop - main/jenkins-lts: normalized package name match | Scoop official bucket manifest trees: bucket/jenkins-lts.json from https://api.github.com/repos/ScoopInstaller/Main/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](https://www.automicvault.com/pkg/brew/jenkins/) - 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-cli](https://www.automicvault.com/pkg/brew/jenkins-cli/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools, jenkins. - [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-lts.yml](https://github.com/automic-vault/db/blob/main/combined/jenkins-lts.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