Another way to uninstall a plugin?

[zil...@gmail.com]

Jenkins v2.346.3 running as a docker container

I go to the Plugins Manager page, click the red-circled "x" and see "Uninstallation pending". I then restart Jenkins via "myJenkins.domain.com/restart", but then see the plugin there again. What gives? Is there a different way to uninstall a plugin? I have access to the $JENKINS_HOME/plugins directory

TIA

Chris

[Björn Pedersen]

zil...@gmail.com schrieb am Sonntag, 1. Januar 2023 um 19:16:34 UTC+1:

Jenkins v2.346.3 running as a docker container

I go to the Plugins Manager page, click the red-circled "x" and see "Uninstallation pending". I then restart Jenkins via "myJenkins.domain.com/restart", but then see the plugin there again. What gives? Is there a different way to uninstall a plugin? I have access to the $JENKINS_HOME/plugins directory

Most probably this plugin is a dependency of another plugin (possibly due to core version dependency if it was a core plugin once), so it gets reinstalled automatically 

 

TIA

Chris

[zil...@gmail.com]

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.

[Daniel Beck]

On Tue, Jan 3, 2023 at 4:49 PM zil...@gmail.com <zil...@gmail.com> 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.

[zil...@gmail.com]

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

[Mark Waite]

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.

[zil...@gmail.com]

Ok I'll try this. Just to be safe I'll just rename my $JENKINS_HOME/plugins directory and the restart the container

[Dirk Heinrichs]

Am Sonntag, dem 08.01.2023 um 16:31 -0800 schrieb zil...@gmail.com:

No it's not the WMI Windows Agents plugin since we're totally a Linux shop.

That plugin is installed regardless of OS.

Bye...

Dirk

-- 

Dirk Heinrichs

Senior Systems Engineer, Delivery Pipeline

OpenText ™ Discovery | Recommind

Phone: +49 2226 15966 18

Email: dhei...@opentext.com

Website: www.recommind.de

Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach

Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.

[Peter Kunst]

Getting rid of the WMI plugin warning implies updating to 2.386 for
me. See https://issues.jenkins.io/browse/JENKINS-70301

Thanks Mark

> --
> 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 jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/eb9cb9a1ff18920f6188d5a79d5dda46afa0781b.camel%40opentext.com.

[Mark Waite]

On Tuesday, January 10, 2023 at 6:32:25 PM UTC-7 Peter wrote:

Getting rid of the WMI plugin warning implies updating to 2.386 for
me. See https://issues.jenkins.io/browse/JENKINS-70301

That's correct.  I've proposed that as an LTS candidate for Jenkins 2.375.3 that will release in about 4 weeks.  If it is not accepted for 2.375.3, then it will be in the next LTS baseline  that will be delivered in 8 weeks.

Mark Waite

[zil...@gmail.com]

So how does the $REF directory get populated? I tried Mar's suggesting and it still didn't work for me.

Chris

On Sunday, January 8, 2023 at 8:07:52 PM UTC-5 Mark Waite wrote: