Issue
Sometimes the Jenkins project might take the decision to stop the distribution of a plugin or a specific version of a plugin.
This can happen for various reasons: blocking issue in the plugin, unfixed security issue, technical issue with a specific release, deprecated by a newer plugin etc…
Environment
- CloudBees CI (CloudBees Core)
- CloudBees CI (CloudBees Core) on modern cloud platforms - Managed Master
- CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
- CloudBees CI (CloudBees Core) on traditional platforms - Client Master
- CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
- CloudBees Jenkins Platform - Client Master
- CloudBees Jenkins Platform - Operations Center
- CloudBees Jenkins Distribution
- Jenkins LTS
Resolution
In such case, the plugin in question should either:
* be updated (if only a specific release distribution has been suspended)
* be uninstalled if the whole plugin distribution has been suspended
If you somehow still need the plugin, please open a support ticket describing your use case (i.e., what goal this plugin helps you achieve).
If you are unsure if the plugin is used, you can follow How to determine if a plugin is in use.
0 Comments