Ok I'll try this. Just to be safe I'll just rename my $JENKINS_HOME/plugins
directory and the restart the container
On Sunday, January 8, 2023 at 8:07:52 PM UTC-5 Mark Waite wrote:
> Removing plugins from Docker containers has some complications that are
> specific to the way plugins are managed in Docker containers. We have a
> work in progress pull request that is developing the detailed description
> of the various scenarios to remove plugins from a container.
>
> The technique that I've used has been to remove the contents of
> ${JENKINS_HOME}/plugins as the last step in my Dockerfile version that is
> removing a plugin so that on the next startup of that container, the
> current set of plugins will be copied from the "${REF}" directory into the
> ${JENKINS_HOME}/plugins directory. I don't know if that's the best way,
> but that's one way that has worked for me.
>
> On Sunday, January 8, 2023 at 5:31:34 PM UTC-7 [email protected] wrote:
>
>> No it's not the WMI Windows Agents plugin since we're totally a Linux
>> shop.
>>
>> I'll try your suggestion of "hovering" the "Uninstall" button. Thanks
>>
>> On Tuesday, January 3, 2023 at 12:36:46 PM UTC-5 [email protected]
>> wrote:
>>
>>> On Tue, Jan 3, 2023 at 4:49 PM [email protected] <[email protected]>
>>> wrote:
>>>
>>>> Thanks. It's a deprecated plugin. I'm trying to uninstall all the
>>>> indicated deprecated plugins, but they just keep coming back after a
>>>> restart. They are disabled though.
>>>>
>>>
>>> Is it WMI Windows Agents Plugin?
>>>
>>> Plugins getting re-installed is expected behavior if they're a plugin
>>> whose functionality was split ("detached") from Jenkins core in the
>>> past, as is the case with that one. It's the only such plugin currently
>>> deprecated as well.
>>>
>>> The only real solution is for all other plugins you have installed to
>>> declare a core dependency of 1.547 or newer, so none of them cause the
>>> detached plugin to be installed automatically again. Check the popup that
>>> appears when hovering the "uninstall" button for candidates, or check the
>>> URL /pluginManager/api/json?tree=plugins[shortName,requiredCoreVersion] in
>>> Jenkins to learn which installed plugins have a ~9 year old core dependency
>>> and should be modernized.
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/22cc86a0-5409-4120-8d8a-40c2527aa972n%40googlegroups.com.
