install

Additional install commands

macOS

Homebrewverified · 100%

brew install jenkins-lts

local Homebrew formula metadata

Windows

Scoopverified · 92%

scoop install main/jenkins-lts

Scoop official bucket manifest trees · bucket/jenkins-lts.json · source: api.github.com

overview

Package summary

Extendable open source continuous integration server

Project links

Commands and aliases

jenkins-lts
jenkins-lts-cli

history

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 posture

Risk level: orange

formula declares a Homebrew service.

Risk classifier

orange risk · medium confidence · infrastructure

Why

formula declares a Homebrew service

Signals

metadata:service

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Formula metadata declares a service or daemon block.
Homebrew bottle metadata is available for 1 platform targets.
Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Unix: $JENKINS_HOME/config.xml$JENKINS_HOME/*.xml$JENKINS_HOME/jobs/[JOBNAME]/config.xml

executables

Installed executables

Command	Kind	Exposure	Note
`jenkins-lts`	cli	global executable
`jenkins-lts-cli`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version2.555.3

manager updated2026-06-26

local dataok

upstreamnot checked

latest detectednot detected

https://www.jenkins.io/

infoRelease/tag comparison is only available for GitHub repositories.https://www.jenkins.io/none confidence

install metadata

Package metadata

Package key	brew:jenkins-lts
Version	2.555.3
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/jenkins-lts
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-stable/2.555.3/jenkins.war
Last updated	2026-06-26T18:36:44+01:00
Pulse	updated
Dependencies	openjdk@21
Bottle	available (on all)
Homebrew post-install	not defined
Service	declared
Caveats	Note: When using launchctl the port will be 8080.

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	jenkins-lts
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Scoop95%

main/jenkins-lts

scoop install main/jenkins-lts

normalized package name match
Matched by: Jenkins Lts

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

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/jenkins-lts.yml

Used sources

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

Install jenkins-lts with Homebrew, scoop