Installer jenkins-lts avec Homebrew, scoop

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• jenkins-lts
• jenkins-lts-cli

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

• 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

• 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/download/lts/