Closed mkrzywanski closed 2 years ago
I tested with Jenkins plugin manager 2.11.1 and the 2.319.1 Docker image and was unable to duplicate the problem. The plugins.txt file that I used was:
azure-keyvault:129.vb7a46bc7b588
azure-vm-agents:797.v31f530348574
build-user-vars-plugin:1.8
cloudbees-folder:6.16
configuration-as-code:1.54
credentials:2.6.1
git:4.9.0
junit:1.47
ldap:2.6
role-strategy:3.2.0
throttle-concurrents:2.4
timestamper:1.13
workflow-aggregator:2.6
ws-cleanup:0.39
The commands that I used to start my test case were:
mkdir plugins
java -jar ../jenkins-plugin-manager-2.11.1.jar \
--jenkins-version 2.319.1 \
--latest false \
--verbose \
--plugin-download-directory plugins \
--plugin-file plugins.txt
JENKINS_HOME=. java -jar ../jenkins-2.319.1.war
When that starts, I move through the install wizard and select to install no plugins (relying on the plugins downloaded). LDAP plugin 2.6 is included in that installation.
I did need to add junit:1.47
to the list of plugins for some reason.
Version report
Jenkins and plugins versions report:
Reproduction steps
plugin.txt
file copied do image.docker-entrypoint.sh
script with following commandplugins.txt
file :2.6
. From the logs I can see that 2.6 plugin is installed :2.6
:Results
When inspecting the ldap plugin version from Jenkins UI it shows that
2.7
version is installed even though I requested2.6
version and logs confirm this version is installed. Also running script in jenkins console shows wrong version2.7
Expected result: Plugin in UI and console script should match the version that is requested and viewed in plugin installation logs.Actual result: Jenkins UI and console scripts show wrong version od requested plugin