MarkEWaite
commented
1 year ago I can't duplicate the problem as described. I wasn't sure of the precise plugin versions installed in the default helm chart so I installed Jenkins 2.387.2 with the plugins and versions listed in the report, then updated the plugins to their latest releases and removed the deprecated plugins. In no case did I see the class not found exception.
Precise plugin versions I used with 2.387.2:
apache-httpcomponents-client-4-api:4.5.14-150.v7a_b_9d17134a_5 authentication-tokens:1.53.v1c90fd9191a_b_ bitbucket:223.vd12f2bca5430 bootstrap5-api:5.2.2-2 bouncycastle-api:2.27 branch-api:2.1071.v1a_188a_562481 caffeine-api:3.1.6-115.vb_8b_b_328e59d8 checks-api:2.0.0 cloudbees-bitbucket-branch-source:800.va_b_b_9a_a_5035c1 cloudbees-folder:6.815.v0dd5a_cb_40e0e command-launcher:100.v2f6722292ee8 commons-lang3-api:3.12.0-36.vd97de6465d5b_ commons-text-api:1.10.0-36.vc008c8fcda_7b_ config-file-provider:3.11.1 credentials:1224.vc23ca_a_9a_2cb_0 credentials-binding:604.vb_64480b_c56ca_ display-url-api:2.3.7 echarts-api:5.4.0-3 font-awesome-api:6.3.0-2 git:5.0.1 git-client:4.2.0 google-oauth-plugin:1.0.8 handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953 htmlpublisher:1.31 instance-identity:142.v04572ca_5b_265 ionicons-api:45.vf54fca_5d2154 jackson2-api:2.15.0-334.v317a_165f9b_7c jakarta-activation-api:2.0.1-3 jakarta-mail-api:2.0.1-3 javax-activation-api:1.2.0-6 javax-mail-api:1.6.2-9 jaxb:2.3.8-1 jdk-tool:66.vd8fa_64ee91b_d job-dsl:1.83 jquery3-api:3.6.4-1 jsch:0.1.55.61.va_e9ee26616e7 junit:1198.ve38db_d1b_c975 mailer:448.v5b_97805e3767 matrix-project:789.v57a_725b_63c79 mercurial:1260.vdfb_723cdcc81 mina-sshd-api-common:2.9.2-62.v199162f0a_2f8 mina-sshd-api-core:2.9.2-62.v199162f0a_2f8 oauth-credentials:0.645.ve666a_c332668 pipeline-graph-analysis:202.va_d268e64deb_3 pipeline-input-step:468.va_5db_051498a_4 pipeline-rest-api:2.32 pipeline-stage-step:305.ve96d0205c1c6 pipeline-stage-view:2.32 pipeline-utility-steps:2.15.2 plain-credentials:143.v1b_df8b_d3b_e48 plugin-util-api:3.2.0 popper2-api:2.11.6-2 scm-api:667.v8b_6e07cdc7f2 script-security:1244.ve463715a_f89c snakeyaml-api:1.33-95.va_b_a_e3e47b_fa_4 ssh-credentials:305.v8f4381501156 sshd:3.275.v9e17c10f2571 structs:324.va_f5d6774f3a_d testcafe:1.0 token-macro:359.vb_cde11682e0c trilead-api:2.84.v72119de229b_7 workflow-api:1208.v0cc7c6e0da_9e workflow-cps:3659.v582dc37621d8 workflow-job:1292.v27d8cc3e2602 workflow-multibranch:746.v05814d19c001 workflow-scm-step:408.v7d5b_135a_b_d49 workflow-step-api:639.v6eca_cd8c04a_a_ workflow-support:839.v35e2736cfd5c
Can you provide the precise list of plugins?
Have you tried updating the plugins to their most recent releases? The Jenkins 2.387.1 changelog notes that HttpClient 3 has been removed from Jenkins core and that Jenkins plugins have been updated to not require HttpClient 3. If you upgrade the Jenkins controller, the guidance is to also upgrade the plugins.
francisco-aguiar-imt
Describe the bug
When jenkins pod is initializing there is in the log the exception below, but initialization ends and the logs says that 'Jenkins is fully up and running'. Everything works, the only odd thing I see is some plugins are not getting updated and I don't know if is related or not.
If not, what could be the cause to ignore the plugins update?
The log:
Version of Helm and Kubernetes
Chart version
4.3.22
What happened?
What you expected to happen?
Plugins get the update
How to reproduce it