Avoid using no longer distributed plugins

Article ID:4402425444635
1 minute readKnowledge base

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…​

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.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.