Removal of deprecated plugin in Jenkins

Using Jenkins Ask a question
,
1

Hello Team,
We are upgrading our jenkins from 2.346.x to 2.426.3
Before the upgrade we see list of deprecated plugins :slight_smile:
The following installed plugins are deprecated
Translation Assistance plugin
Popper.js API Plugin
JavaScript GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin
DEPRECATED Blue Ocean Executor Info
Icon Shim
Bootstrap 4 API Plugin
JavaScript GUI Lib: ACE Editor bundle plugin
GitHub Organization Folder Plugin
WMI Windows Agents Plugin
Pipeline: Declarative Agent API
Pipeline: Deprecated Groovy Libraries
JavaScript GUI Lib: Handlebars bundle plugin
Static Analysis Utilities
JavaScript GUI Lib: Moment.js bundle plugin
Violations plugin

Code Coverage API Plugin
Popper.js 2 API Plugin

Now the question is we have alternatives of plugins, which is fine. Lets take an example of Popper.js 2 API Plugin which has 2 dependant plugin. But there might be scenario where Pipper.js 2 API plugin must be dependant on any other plugin. Is there a way to figure out the dependecies ? and also is there a way or script to figure out which jobs are using which plugins ?

Since plugin usage plugin is experimental it s not going to help us.

2

I think you’re interpreting it wrong. poppers.js 2 API plugin depends on 2 other plugins but there are no other plugins that depend on it. So it is safe to remove it.
Same is true for all the Javascript Gui lib plugins
Other plugins that can be safely removed:
Icon Shim
WMI Windows agents
Translation assistance plugin

1 Like
3

Additionally, if you want to ensure no loss of functionality; you can disable the plug-in and run Jenkins for a stretch to ensure no issues.

At least with a disable, configurations don’t need to get put back in; and “roll backs” are instant.

1 Like