Jenkins plugins incompatible

Using Jenkins
,
1

Hi All,

We have Jenkins running in AKS with the below Jenkins Setup details provided.

We are running an older version of Jenkins, while installing the plugins we are facing the below issues .

  1. Jenkins Jobs are missing post installing a particular plugin, although we reduced the version using CLI and trying to find the right plugin version The same issue is repeating for multiple Plugins.

Async Http client
Cucumber reports
Cucumber-perf
Environment Dashboard
Join
Log Parser
Mask Passwords
Next Build Number
Node and Label parameter
Publish Over CIFS
Validating String Parameter
Artifact Deployer
Scriptler

2.Plugin version incompatible and stating multiple dependent Plugins are missing.
Is there any way to identify the plugins version compatible for mentioned jenkins version ?

Jenkins setup: 
Jenkins: 2.346.2
OS: Linux - 5.15.0-1036-azure
Java: 11.0.15 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
---
ace-editor:1.1
active-directory:2.23
amazon-ecr:1.6
ansicolor:1.0.0
ant:1.11
antisamy-markup-formatter:2.1
apache-httpcomponents-client-4-api:4.5.13-1.0
authentication-tokens:1.4
aws-credentials:1.29
aws-java-sdk:1.11.995
azure-acs:1.0.4
azure-ad:267.v5b_dfb_514d9fd
azure-commons:1.1.3
azure-container-agents:210.v8071dd1c9f3f
azure-container-registry-tasks:0.6.5
azure-credentials:182.v3ccd4a755864
azure-credentials-ext:1.0
azure-keyvault:116.v4c0cbc857be0
azure-sdk:118.v43f74dd9ca_dc
badge:1.8
blueocean-commons:1.24.8
blueocean-core-js:1.24.8
blueocean-dashboard:1.24.8
blueocean-git-pipeline:1.24.8
blueocean-github-pipeline:1.24.8
blueocean-jwt:1.24.8
blueocean-pipeline-api-impl:1.24.8
blueocean-pipeline-editor:1.24.8
blueocean-pipeline-scm-api:1.24.8
blueocean-rest:1.24.8
blueocean-rest-impl:1.24.8
blueocean-web:1.24.8
bootstrap4-api:4.6.0-3
bootstrap5-api:5.1.1-1
bouncycastle-api:2.25
branch-api:2.6.5
build-pipeline-plugin:1.5.8
build-timeout:1.20
build-timestamp:1.0.3
caffeine-api:2.9.3-65.v6a_47d0f4d1fe
checks-api:1.7.2
cloud-stats:0.27
cloudbees-disk-usage-simple:0.10
cloudbees-folder:6.740.ve4f4ffa_dea_54
command-launcher:1.6
conditional-buildstep:1.4.1
config-file-provider:3.8.0
configuration-as-code:1512.vb_79d418d5fc8
copyartifact:1.46
credentials:1143.vb_e8b_b_ceee347
credentials-binding:1.27.1
dashboard-view:2.17
discard-old-build:1.05
display-url-api:2.3.6
docker-build-publish:1.3.3
docker-build-step:2.7
docker-commons:1.17
docker-compose-build-step:1.0
docker-java-api:3.1.5.2
docker-plugin:1.2.2
docker-workflow:1.26
durable-task:1.39
dynamic_extended_choice_parameter:1.0.1
echarts-api:5.2.1-2
email-ext:2.82
envfile:1.2
envinject:2.4.0
envinject-api:1.7
extended-choice-parameter:0.82
extended-read-permission:3.2
extended-security-settings:1.3
external-monitor-job:1.7
favorite:2.3.3
file-operations:1.11
file-parameters:99.102.vbc6a133bcbbb
filesystem-list-parameter-plugin:0.0.7
font-awesome-api:5.15.4-1
git:4.11.4
git-client:3.11.2
git-parameter:0.9.13
git-server:1.9
github:1.34.5
github-api:1.123
github-branch-source:2.10.2
gitlab-api:1.0.6
gitlab-branch-source:1.5.6
google-kubernetes-engine:0.8.6
google-oauth-plugin:1.0.5
gradle:1.36
groovy:2.4
groovy-postbuild:2.5
h2-api:1.4.199
handlebars:3.0.8
handy-uri-templates-2-api:2.1.8-1.0
htmlpublisher:1.25
hudson-wsclean-plugin:1.0.8
icon-shim:3.0.0
jackson2-api:2.13.0-230.v59243c64b0a5
javadoc:1.6
javax-activation-api:1.2.0-3
javax-mail-api:1.6.2-6
jaxb:2.3.0
jdk-tool:1.5
jenkins-design-language:1.24.8
jjwt-api:0.11.2-9.c8b45b8bb173
jobConfigHistory:2.27
jquery:1.12.4-1
jquery-detached:1.2.1
jquery3-api:3.6.0-2
jsch:0.1.55.2
junit:1.53
kubernetes:1.30.1
kubernetes-cd:2.3.1
kubernetes-client-api:5.4.1
kubernetes-credentials:0.9.0
kubernetes-credentials-provider:0.20
kubernetes-pipeline-devops-steps:1.6
ldap:2.6
lockable-resources:2.12
m2release:0.16.2
mailer:414.vcc4c33714601
managed-scripts:1.5.4
mapdb-api:1.0.9.0
matrix-auth:3.1.5
matrix-project:772.v494f19991984
maven-info:0.3.0
maven-metadata-plugin:2.0.0
maven-plugin:3.12
metrics:4.0.2.8
momentjs:1.1.1
multiple-scms:0.6
oauth-credentials:0.4
okhttp-api:4.9.3-108.v0feda04578cf
pam-auth:1.6
parameterized-scheduler:1.0
parameterized-trigger:2.40
pipeline-build-step:2.15
pipeline-github-lib:1.0
pipeline-graph-analysis:1.11
pipeline-input-step:2.12
pipeline-maven:3.10.0
pipeline-milestone-step:1.3.2
pipeline-model-api:1.9.3
pipeline-model-declarative-agent:1.1.1
pipeline-model-definition:1.9.3
pipeline-model-extensions:1.9.3
pipeline-rest-api:2.19
pipeline-stage-step:2.5
pipeline-stage-tags-metadata:1.9.3
pipeline-stage-view:2.19
pipeline-utility-steps:2.8.0
plain-credentials:139.ved2b_9cf7587b
plugin-util-api:2.5.0
popper-api:1.16.1-2
popper2-api:2.10.2-1
pubsub-light:1.13
rebuild:1.32
repository:1.3
resource-disposer:0.15
role-strategy:3.1.1
run-condition:1.5
saferestart:0.3
scm-api:608.vfa_f971c5a_a_e9
scmskip:1.0.3
script-security:1138.v8e727069a_025
scriptler:3.5
shared-objects:0.44
show-build-parameters:1.0
snakeyaml-api:1.32-86.ve3f030a_75631
ssh-agent:295.v9ca_a_1c7cc3a_a_
ssh-credentials:305.v8f4381501156
ssh-slaves:1.834.v622da_57f702c
sshd:3.0.3
structs:318.va_f3ccb_729b_71
subversion:2.14.0
svn-workspace-cleaner:1.1
text-file-operations:1.3.2
text-finder:1.15
thinBackup:1.10
timestamper:1.13
token-macro:293.v283932a_0a_b_49
trilead-api:1.67.vc3938a_35172f
uno-choice:2.5.6
variant:1.4
view-job-filters:2.3
windows-azure-storage:359.v09573e5ff73f
windows-slaves:1.8
workflow-aggregator:2.6
workflow-api:1153.vb_912c0e47fb_a_
workflow-basic-steps:2.24
workflow-cps:2633.v6baeedc13805
workflow-cps-global-lib:2.21
workflow-durable-task-step:2.40
workflow-job:1145.v7f2433caa07f
workflow-multibranch:2.26
workflow-scm-step:2.13
workflow-step-api:639.v6eca_cd8c04a_a_
workflow-support:3.8
ws-cleanup:0.39
2

Welcome @angrycapry:
A couple questions to start.

What version of Jenkins are you running?
What error Messages are you seeing? Why do you think some plug ins are missing?
I assume you are installing and upgrading plug-ins thru the GUI? To what level are you upgrading plug-ins? As you upgrade, IIRC, there is an option to upgrade to the Highest-Compatible version.

This was a useful plugin for me (Plugin Usage) while I was trying to gather information about plug ins. When I was ‘weeding’ my plug in garden, I found that I had plugins that were deprecated for various reasons, as that plug in was deprecated it caused other plug ins to fail to load. I used this plug in to find the threads that failed and follow it all the way to the source.

Good Luck and Happy New Year!

3

Summary: If you must remain on Jenkins 2.346.2, then it is probably best that you also choose to remain with exactly the plugins that you had installed at the time you decided to remain with Jenkins 2.346.2.

Details

The Jenkins update center provides the list of available plugins, the minimum Jenkins versions required by those versions, and the dependencies of those plugins. The update site generator maintains the Jenkins update center. However, the Jenkins update center only provides data for roughly 15 months worth of Jenkins releases. The Jenkins version you are running is no longer included in the Jenkins update center.

The “choosing a Jenkins version” page (for plugin developers to select the minimum baseline for plugins they maintain) advises:

  • Do not use versions no longer supported by the update center, which is currently anything older than 2.377 for weekly releases, and 2.361.4 for LTS releases. Note that the lowest supported version changes about every week (weekly release) or every month (LTS release), so these specific versions will be a bad choice soon.

Note that it says that Jenkins versions older than 2.377 (weekly) and 2.361.4 (LTS) are not supported by the Jenkins update center.

When your Jenkins 2.346.2 controller requests data from the Jenkins update center, it is given the data for the oldest version supported by the update center. At the moment, that is Jenkins 2.361.4. In less than a month, that will be Jenkins 2.375.1. The Jenkins plugin manager inside Jenkins 2.346.2 then offers plugin upgrades based on the data it received. Those offered upgrades may include plugins that will not work in your Jenkins 2.346.2

The Jenkins project provides security updates for the most recent weekly release (currently 2.438) and the most release LTS release (currently 2.426.2). Jenkins 2.346.2 has multiple known security vulnerabilities. Plan your upgrade to a newer Jenkins version.

4

Hi Mark,

Thanks for the quick response.

understand details shared by you . I will look into whether I can upgrade the jenkins to the versions recommended by you which are (older than 2.377 for weekly releases, and 2.361.4 for LTS releases) .

Is there any possibility for checking the supported plugins versions for a selected Jenkins version, this will help us to move forward with the manual plugins installation with the specific plugins version supported by Jenkins. 2.346.2.

regards
kishore

5

For clarity, I recommend that you upgrade to the most recent Jenkins LTS and that you plan to upgrade every 4 weeks to the next Jenkins LTS release. Choosing to remain on an older Jenkins version is a choice to save a little time every four weeks and then to spend much, much more time and effort later by upgrading across Jenkins multiple versions.

Yes, there is a possibility to check the supported plugin versions for a selected Jenkins version. Every plugin binary file includes a manifest that lists the minimum Jenkins version it requires and the plugins on which it depends. You could extract that dependency information yourself and do the dependency resolution yourself to assure that none of the dependencies require a newer Jenkins version.

You could also explain to the security people in your organization why you are intentionally continuing to run a Jenkins version with known security vulnerabilities rather than upgrading to a version that resolves those vulnerabilities.

I don’t think that it is wise to remain on an outdated Jenkins version and continue to update plugins. If you’re stuck on an outdated Jenkins version, then you’re stuck on outdated plugins. If you want newer plugins, then upgrade to a new version of Jenkins core.