@oleg-nenashev and @timja do you think it is a good idea to name the binary jenkins-plugin-manager and the script jenkins-plugin-manager-script. This will help the user to identify easily as jenkins tools in their custom "scripts". Rename the tool to Plugin Manager (Tool) in the documentation, since, the tool does a lot more than just installing the plugin.
so no -1
@MarkEWaite When I am documenting the tool, I am not making an effort to take about plugin management per se, The document´s focus is to document the functionality of the tool from a user perspective.
Hi, I've set the following environment variables:
- name: JENKINS_UC
value: "http://updates.jenkins.io"
- name: JENKINS_UC_EXPERIMENTAL
value: "http://updates.jenkins.io/experimental"
- name: JENKINS_INCREMENTALS_REPO_MIRROR
value: "http://repo.jenkins-ci.org/incrementals"
- name: JENKINS_PLUGIN_INFO
value: "http://updates.jenkins.io/plugin-versions.json"Yet still (according to the log), it is trying to download plugins from https://get.jenkins.io:
"Tried downloading <plugin> from https://get.jenkins.io/plugins/<plugin>"
Any ideas?
what are you trying to achieve though? you have some weird proxy that doesn't work with ssl?
done, still "Tried downloading <plugin> from https://get.jenkins.io/plugins/" with:
- name: JENKINS_UC_DOWNLOAD
value: "http://updates.jenkins.io/download"
Yes I'm behind proxy that does a man-in-the-middle attack. Easiest way around is to use http endpoints instead of https
Proper solution would be to add the company CA certificate to trusted store. Perhaps I should try that instead. "Easy" option isn't turning out to be very easy
:-)
"add the company CA certificate to trusted store" - hopefully the helm chart I'm using allows this...
Howdy folks, any insight on how I can pin just one specific plugin version which is a dependency of another plugin? Specifically need to pin down
I am aware that I should upgrade so i can ran up-to-date dependencies, but having ability to pin just one or two dependencies would be super neat. Alternative of running jenkins-plugin-manager with
kubernetes-client-api:4.13.3-1 because its next version (5.4.1) has breaking API changes for kubernetes:1.27.7 which is the latest version that can run on my Jenkins v2.249.3. As somewhat expected I am getting Plugin kubernetes:1.27.7 depends on kubernetes-client-api:5.4.1, but there is an older version defined on the top level - kubernetes-client-api:4.13.3-1 while my jenkins is starting up and preloading plugins.I am aware that I should upgrade so i can ran up-to-date dependencies, but having ability to pin just one or two dependencies would be super neat. Alternative of running jenkins-plugin-manager with
--latest false flag also doesn't work for me since it results in much lower versions for multiple other plugins.
7 replies
Hi guys. So i'm trying to install git plugin for jenkins and i obtain this
turns out i have to manually install all of those plugins first
so i tried this command java -jar C:\Windows\System32\config\systemprofile\AppData\Local\Jenkins\jenkins-plugin-manager-2.9.2.jar --war C:\Windows\System32\config\systemprofile\AppData\Local\Jenkins\war --plugin-file C:\Windows\System32\config\systemprofile\AppData\Local\Jenkins\plugins.txt --plugins delivery-pipeline-plugin:1.3.2 deployit-plugin
and i obtain this error Error getting update center json
do you guys have an idea of what i should do please?
And sorry for annoying
Hello - when hitting https://updates.jenkins.io/update-center.json?version=2.277.3 I get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json which serves up the update json for 2.289.2. I believe this is causing the plugin manager CLI to pull in "latest" for 2.289.2 instead of being restrained to "latest" of 2.277.3. Where can I get the 2.277.3 update-center.json file? I can't seem to find it anywhere.
Yea that's a red herring that threw me off. What we are seeing is the wrong minimum dependency version being required.
The active-directory:2.23 plugin depends on configuration-as-code:1.35 pom.xml. However the CLI is claiming it needs 1.51:
$ java -jar jenkins-plugin-manager-2.10.0.jar --jenkins-version 2.277.3 --plugins active-directory:2.23 configuration-as-code:1.46
War not found, installing all plugins: C:\ProgramData\Jenkins\jenkins.war
Plugin prerequisite not met:
Plugin active-directory:2.23 depends on configuration-as-code:1.51, but there is an older version defined on the top level - configuration-as-code:1.46
If your intent is to install the exact version specified in the plugins.txt file, then you need the argument
--latest false. However, that usually also means that you then need to define the precise version of all your plugins. The plugin installation manager tool wants to offer you the most recent versions of unspecified plugins that are compatible with your Jenkins core version. Refer to jenkinsci/plugin-installation-manager-tool#250 for more details about the behavior
So I'm trying to fix a weird issue with the plugin-installation-manager-cli-tool and dependency resolution. The short story is that JCasC won't load because the version of caffeine-api is too old. The
plugins.yaml file pins caffeine-api to 2.9.2-29.v717aac953ff3, which is the same version required by JCasC. However, script-security (pinned to 1.78, the current latest version) seems to want to install 2.9.1-23.v51c4e2c879c8. Looking at the pom.xml file for script-security, it doesn't seem to specify a version for caffeine-api version there, so I have no idea why it picks that version, and then why this version gets used instead of the version that I explicitly requested in plugins.yaml.
2 replies
Also I should note that we are running the tool (version 2.11.1) with
--latest false, in case that should make a difference.
Here's the
plugins.yaml file: https://gist.github.com/nre-ableton/147c7439d74a5512bbcb1ba90eeb4740
And the corresponding command to install plugins is:
java -jar /opt/jenkins/lib/jenkins-plugin-manager-2.11.1.jar --plugin-download-directory /tmp/plugins --plugin-file /opt/jenkins/config/plugins.yaml --war /opt/jenkins/lib/jenkins-2.319.1.war --latest false --verbose
The Jenkins that starts from your plugins.yaml file works well for me with the following commands:
$ rm -rf plugins
$ mkdir plugins
$ java -jar ../jenkins-plugin-manager-2.11.1.jar --jenkins-version 2.319.1 --latest false --plugin-download-directory plugins --plugin-file plugins.yaml
$ JENKINS_HOME=. java -jar ../jenkins-2.319.1.warWhen the Jenkins install wizard appears after those commands, I choose to install no additional plugins. As far as I can tell, it is running the versions of plugins that are specified in the plugins.yaml file without any complaint. I wonder if your /tmp/plugins directory might not be empty and the existing files are causing some difference in behavior compared to what I see? I didn't check every plugin version, but I did confirm there are several plugins that need updates.
@MarkEWaite We delete
/tmp/plugins before running the tool to ensure there is no stale data from a previous deployment. After we run the plugin manager tool, we copy everything from /tmp/plugins to the Jenkins plugins directory (we do this because we are using Ansible and we want to see which plugins were changed during the copy). So in addition to the stuff in plugins.yaml, we are installing a few other plugins by hand, namely snakeyaml-api @ 1.29.1, JCasC @1.55, caffeine-api @ 2.9.2-29.v717aac953ff3.hpi, and two custom plugins specific to my company. These plugins are copied directly to the Jenkins plugin directory after running the tool.
So we somehow end up with two versions of
caffeine-api, and the canonical one is the older one, so JCasC won't start.
In the log for the plugin installation tool step, I see this output:
script-security depends on:
caffeine-api 2.9.1-23.v51c4e2c879c8
Setting checksum for: caffeine-api to W8xSQEQ+gm6jmyWP1n5sSX+71OxHoxb7y939vfS8h2s=
@MarkEWaite I would be interested in seeing your logfile to see what
script-security wants
@itdtin see https://www.jenkins.io/doc/book/installing/offline/ for the current best suggestions for offline installation.
Hi everyone, Has anyone have done any POC for this issue jenkinsci/plugin-installation-manager-tool#93.