# Deleted plugins keeps coming back after jenkins restart

**URL:** <https://community.jenkins.io/t/deleted-plugins-keeps-coming-back-after-jenkins-restart/14949>\
**Category:** Ask a question\
**Tags:** question\
**Created:** [May 8, 2024, 2:29pm UTC](https://community.jenkins.io/t/deleted-plugins-keeps-coming-back-after-jenkins-restart/14949 "2024-05-08T14:29:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samet](https://avatars.discourse-cdn.com/v4/letter/s/ea5d25/32.png) [@Samet](https://community.jenkins.io/u/Samet)\
**Post date:** [May 8, 2024, 2:29pm UTC](https://community.jenkins.io/t/deleted-plugins-keeps-coming-back-after-jenkins-restart/14949/1 "2024-05-08T14:29:42Z")

</div>

## Jenkins setup: Jenkins: 2.426.3 OS: Linux - 5.10.210-201.855.amzn2.x86\_64 Java: 17.0.9 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)

ace-editor:1.1  
amazon-ecr:1.114.vfd22430621f5  
antisamy-markup-formatter:162.v0e6ec0fcfcf6  
apache-httpcomponents-client-4-api:4.5.14-208.v438351942757  
asm-api:9.7-33.v4d23ef79fcc8  
authentication-tokens:1.53.v1c90fd9191a\_b\_  
authorize-project:1.7.1  
aws-credentials:231.v08a\_59f17d742  
aws-java-sdk-api-gateway:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-autoscaling:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-cloudformation:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-cloudfront:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-codebuild:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-codedeploy:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-ec2:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-ecr:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-ecs:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-efs:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-elasticbeanstalk:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-elasticloadbalancingv2:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-iam:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-kinesis:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-lambda:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-logs:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-minimal:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-organizations:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-secretsmanager:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-sns:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-sqs:1.12.671-445.ve02f9b\_558f2e  
aws-java-sdk-ssm:1.12.671-445.ve02f9b\_558f2e  
bootstrap5-api:5.3.3-1  
bouncycastle-api:2.30.1.77-225.v26ea\_c9455fd9  
branch-api:2.1152.v6f101e97dd77  
build-name-setter:2.4.2  
build-user-vars-plugin:1.9  
caffeine-api:3.1.8-133.v17b\_1ff2e0599  
checks-api:2.0.2  
cloudbees-folder:6.858.v898218f3609d  
command-launcher:100.v2f6722292ee8  
commons-lang3-api:3.13.0-62.v7d18e55f51e2  
commons-text-api:1.11.0-95.v22a\_d30ee5d36  
configuration-as-code:1775.v810dc950b\_514  
copyartifact:722.v0662a\_9b\_e22a\_c  
credentials:1337.v60b\_d7b\_c7b\_c9f  
credentials-binding:657.v2b\_19db\_7d6e6d  
display-url-api:2.200.vb\_9327d658781  
docker-commons:439.va\_3cb\_0a\_6a\_fb\_29  
durable-task:550.v0930093c4b\_a\_6  
echarts-api:5.5.0-1  
extended-choice-parameter:381.v360a\_25ea\_017c  
font-awesome-api:6.5.1-3  
git:5.2.1  
git-client:4.7.0  
git-parameter:0.9.19  
git-server:114.v068a\_c7cc2574  
google-chat-notification:141.va\_4b\_b\_6a\_25483c  
gson-api:2.10.1-15.v0d99f670e0a\_7  
instance-identity:185.v303dc7c645f9  
ionicons-api:70.v2959a\_b\_74e3cf  
jackson2-api:2.17.0-379.v02de8ec9f64c  
jakarta-activation-api:2.1.3-1  
jakarta-mail-api:2.1.3-1  
javax-activation-api:1.2.0-6  
javax-mail-api:1.6.2-9  
jaxb:2.3.9-1  
jdk-tool:73.vddf737284550  
joda-time-api:2.12.7-29.v5a\_b\_e3a\_82269a\_  
jquery3-api:3.7.1-2  
jsch:0.1.55.2  
json-api:20240303-41.v94e11e6de726  
json-path-api:2.9.0-58.v62e3e85b\_a\_655  
junit:1265.v65b\_14fa\_f12f0  
kubernetes:4203.v1dd44f5b\_1cf9  
kubernetes-cli:1.12.1  
kubernetes-client-api:6.10.0-240.v57880ce8b\_0b\_2  
kubernetes-credentials:0.11  
locale:431.v3435fa\_8f8445  
mailer:470.vc91f60c5d8e2  
matrix-auth:3.2.2  
matrix-project:822.824.v14451b\_c0fd42  
metrics:4.2.21-449.v6960d7c54c69  
mina-sshd-api-common:2.12.1-101.v85b\_e08b\_780dd  
mina-sshd-api-core:2.12.1-101.v85b\_e08b\_780dd  
okhttp-api:4.11.0-172.vda\_da\_1feeb\_c6e  
pipeline-aws:1.45  
pipeline-build-step:540.vb\_e8849e1a\_b\_d8  
pipeline-graph-analysis:216.vfd8b\_ece330ca\_  
pipeline-groovy-lib:704.vc58b\_8890a\_384  
pipeline-input-step:477.v339683a\_8d55e  
pipeline-milestone-step:119.vdfdc43fc3b\_9a\_  
pipeline-model-api:2.2184.v0b\_358b\_953e69  
pipeline-model-definition:2.2184.v0b\_358b\_953e69  
pipeline-model-extensions:2.2184.v0b\_358b\_953e69  
pipeline-rest-api:2.34  
pipeline-stage-step:312.v8cd10304c27a\_  
pipeline-stage-tags-metadata:2.2184.v0b\_358b\_953e69  
pipeline-stage-view:2.34  
plain-credentials:179.vc5cb\_98f6db\_38  
plugin-util-api:4.1.0  
popper2-api:2.11.6-1  
prism-api:1.29.0-13  
role-strategy:713.vb\_3837801b\_8cc  
saml:4.464.vea\_cb\_75d7f5e0  
scm-api:689.v237b\_6d3a\_ef7f  
script-security:1326.vdb\_c154de8669  
simple-theme-plugin:176.v39740c03a\_a\_f5  
slack:684.v833089650554  
snakeyaml-api:2.2-111.vc6598e30cc65  
ssh-credentials:337.v395d2403ccd4  
sshd:3.322.v159e91f6a\_550  
structs:337.v1b\_04ea\_4df7c8  
thinBackup:1.19  
token-macro:400.v35420b\_922dcb\_  
trilead-api:2.142.v748523a\_76693  
uno-choice:2.8.3  
variant:60.v7290fc0eb\_b\_cd  
workflow-aggregator:596.v8c21c963d92d  
workflow-api:1291.v51fd2a\_625da\_7  
workflow-basic-steps:1049.v257a\_e6b\_30fb\_d  
workflow-cps:3894.vd0f0248b\_a\_fc4  
workflow-cps-global-lib:2.19  
workflow-durable-task-step:1331.vc8c2fed35334  
workflow-job:1385.vb\_58b\_86ea\_fff1  
workflow-multibranch:773.vc4fe1378f1d5  
workflow-scm-step:427.v4ca\_6512e7df1  
workflow-step-api:657.v03b\_e8115821b\_  
workflow-support:896.v175a\_a\_9c5b\_78f  
Hi,  
I am trying to manage jenkins plugins with helm values.yaml config file. When I compare my config file with plugin list in Dashboard =\> Manage Jenkins =\> Plugins =\> Installed plugins, I saw that values.yaml does not incluede plugins workflow-cps-global-lib, popper2-api, jsch,ace-editor, javax-mail-api, command-launcher,aws-java-sdk. I checked them on Jenkins dashboard and see I can uninstall them (so they are not dependency to other plugins) to sync plugin config with actual state. However they enter _Uninstallation pending_ state, comes back when I restart jenkins. How can I delete these plugins and what could be the reason of this situation?  
Thank you

---

<div class="post-metadata">

**Author:** ![sodul](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/sodul/32/7828_2.png) [@sodul](https://community.jenkins.io/u/sodul)\
**Post date:** [May 8, 2024, 8:57pm UTC](https://community.jenkins.io/t/deleted-plugins-keeps-coming-back-after-jenkins-restart/14949/2 "2024-05-08T20:57:40Z")

</div>

I noticed a similar issue but with fewer plugins than you. Several plugins used to be part of the core of Jenkins such as maven, svn, etc… and these would always come back no matter what I did. In newer versions of Jenkins this seems to have improved but I still see a few remaining plugins that always come back. We are on the latest 2.440 LTS so there are less of these plugins, so maybe you can try with 2.440 and see if you are able to get rid of more plugins.

I would check the version of your helm chart as well. The init container logic has changed in newer versions. We are still on an older chart (v3.x IIRC), but we plan on upgrading to the latest chart as soon as we get some free cycles to test and deploy it (older chart upgrades broke many things, but that should not be the case anymore).

---

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [May 13, 2024, 5:45pm UTC](https://community.jenkins.io/t/deleted-plugins-keeps-coming-back-after-jenkins-restart/14949/3 "2024-05-13T17:45:59Z")

</div>

The issue you’re experiencing might be due to the fact that these plugins may be dependencies of other plugins that are still installed in your Jenkins instance. Even if the Jenkins UI doesn’t explicitly list them as dependencies, they might still be required by other plugins. 🤷

---

<div class="post-metadata">

**Author:** ![mawinter69](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/mawinter69/32/1625_2.png) [@mawinter69](https://community.jenkins.io/u/mawinter69)\
**Post date:** [May 13, 2024, 6:32pm UTC](https://community.jenkins.io/t/deleted-plugins-keeps-coming-back-after-jenkins-restart/14949/4 "2024-05-13T18:32:25Z")

</div>

Plugins like ace-editor are obsolete. They can be uninstalled and they should not come back. This can only happen when there is some other process, that fills the plugins directory.  
Some other plugins like javax-mail-api will come back if you have an older plugin installed that might implicitly depend on it. I was also not able to permanently remove. But what works is to disable the plugin and then it stayed disabled.