JENKINS-41745: Deprecate the Remoting-based protocol for the Jenkins CLI feature. Enhance the client and server to conveniently perform most existing CLI tasks with simpler and safer protocols.
daniel-beck
/ JENKINS-41745-proposal.md
Created
April 9, 2017 20:16
— forked from jglick/JENKINS-41745-proposal.md
Proposal for JENKINS-41745: Remoting-free CLI
daniel-beck
/ jenkinsci-advisories.txt
Created
August 31, 2021 11:19
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Subject: Jenkins plugins security advisory | |
| The following Jenkins plugin updates contain fixes for security vulnerabilities: | |
| * Azure AD Plugin 180.v8b1e80e6f242 | |
| * Code Coverage API Plugin 1.4.1 | |
| * Nested View Plugin 1.21 | |
| * Nomad Plugin 0.7.5 | |
| * SAML Plugin 2.0.8 |
daniel-beck
/ readme.adoc
Last active
July 16, 2022 15:08
Plugin management on older Jenkins releases
During development, we sometimes need to figure out whether a behavior is a regression, or just in general to see how Jenkins used to behave in the past. This is complicated by update sites only being generated for the last year of Jenkins releases, and older Jenkinses will fail to install plugins that have too recent minimum requirements. This document explains how to work around that.
Jenkins infrastructure uses mirrors to distribute update site downloads and metadata. These mirrors are not automatically cleaned up, so when the project stops publishing an update site tier (~ downloads for a specific version of Jenkins), those remain available on mirrors.