-
Bug
-
Resolution: Duplicate
-
Minor
-
None
Jenkins depends on 3rd-party plugins for basic functionality. These plugins break from time to time, giving the end user a bad experience.
I would like to propose the Jenkins project elect a set of core features that depend on external plugins and ensure these are well maintained and pass all tests before a new release of Jenkins if published.
Anyone that has been maintaining Jenkins for a little while must have experienced that new plugin upgrade that breaks things. It becomes a daunting tasks for all admins to do this curating process. Everybody would benefit if this was done top-down.
For example, if Jenkins thinks a GitHub PR builder functionality is a core feature (even though it's in a plugin), then this shouldn't happen. This situation (new plugin upgrade -> breakage) happens all the time.
- duplicates
-
JENKINS-30967 Curate default plugins directory - eliminate outdated and low quality plugins
- Resolved