Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jul 26 21:20
    MarkRx commented #353
  • Jul 26 21:07
    MarkRx edited #353
  • Jul 26 21:03
    MarkRx labeled #353
  • Jul 26 21:03
    MarkRx opened #353
  • Jul 26 08:05

    timja on master

    Bump slf4j-api from 1.7.31 to 1… (compare)

  • Jul 26 08:05

    timja on maven

    (compare)

  • Jul 26 08:05
    timja closed #352
  • Jul 26 07:00
    dependabot[bot] labeled #352
  • Jul 26 07:00
    dependabot[bot] opened #352
  • Jul 26 07:00

    dependabot[bot] on maven

    Bump slf4j-api from 1.7.31 to 1… (compare)

  • Jul 26 06:26
    AssafKatz3 commented #351
  • Jul 25 15:10
    AssafKatz3 commented #351
  • Jul 25 15:01
    timja commented #351
  • Jul 25 13:00
    AssafKatz3 commented #351
  • Jul 25 12:53
    timja commented #351
  • Jul 25 12:48
    AssafKatz3 opened #351
  • Jul 25 12:48
    AssafKatz3 labeled #351
  • Jul 23 02:02
  • Jul 22 12:14
    savujevi commented #333
  • Jul 19 07:08

    timja on maven

    (compare)

hp77
@hp77-creator
Oleg, I am really sorry, The electricity just went away at my place and I got disconnected.
hp77
@hp77-creator
Thank you for recording the session. Please share the link when its uploaded, I couldn't hear your explanation for my last doubt on maven repository as an installation source.
Oleg Nenashev
@oleg-nenashev
Sure, will do
Oleg Nenashev
@oleg-nenashev
Recording will be here: https://youtu.be/QJcwcLnHjRw . Now processing. FYI @hp77-creator
1 reply
Ryan Berger
@ryanberger-az
where is the jenkins-plugin-cli located by default? i see it referenced in a lot of the git repo's for plugins, but i am not sure what program natively lives when you install jenkins to be able to run it!
commands like: jenkins-plugin-cli --plugins azure-vm-agents:779.v5ea1414ec40f
Tim Jacomb
@timja
Thats just a shell script in the jenkins docker image running https://github.com/jenkinsci/plugin-installation-manager-tool
ncook-hxgn
@ncook-hxgn
image.png

Hi there, noob here, think I'm caught on a probably dumb thing.

I'm trying to get a list of plugins out of my existing Jenkins instance, so that I can set up a preprod environment to test Jenkins updates and such with out plugins

So far I'm not having much luck.. I'm hoping that whatever I've not done is really obvious.. I didn't think it was worth creating a Github issue for

ncook-hxgn
@ncook-hxgn
@timja I will give it a go, thank you kindly :)
@timja works like a charm, son! Thanks again :) Pre-prod here we go! :D
yr-sudhakar
@yr-sudhakar
Should the plugin-install-manager have a command line parameter to list all the plugins installed in a Jenkins controller? This output can be used to with the this tool can be used to rapidly install multiple and identical Jenkins controllers.
4 replies
yr-sudhakar
@yr-sudhakar
I was trying to use plugin-install-manager tool to document. Couple of days ago the tool was trying to reach the Jenkins mirror site in *.cn domain and timeout. Now, wget on
yr-sudhakar
@yr-sudhakar

hit enter by mistake earlier, A continuation .... Now, wget on https://get.jenkins.io/plugins/kubernetes-plugin/1.29.2/kubernetes-plugin.hpi and https://get.jenkins.io/plugins/kubernetes-plugin do not succeed. Wher
eas https://get.jenkins.io/plugins/kubernetes-plugin succeeds. Any comments on how to resolve it. More details follow.

wget https://get.jenkins.io/plugins/kubernetes-plugin/1.29.2/kubernetes-plugin.hpi -v
--2021-05-17 19:49:07-- https://get.jenkins.io/plugins/kubernetes-plugin/1.29.2/kubernetes-plugin.hpi
Resolving get.jenkins.io (get.jenkins.io)... 52.167.253.43
Connecting to get.jenkins.io (get.jenkins.io)|52.167.253.43|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-05-17 19:49:09 ERROR 404: Not Found.

wget https://get.jenkins.io/plugins/kubernetes-plugin/1.29.2/kubernetes-plugin.hpi -v
--2021-05-17 19:50:37-- https://get.jenkins.io/plugins/kubernetes-plugin/1.29.2/kubernetes-plugin.hpi
Resolving get.jenkins.io (get.jenkins.io)... 52.167.253.43
Connecting to get.jenkins.io (get.jenkins.io)|52.167.253.43|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-05-17 19:50:39 ERROR 404: Not Found.

wget https://get.jenkins.io/plugins/kubernetes-plugin -v
--2021-05-17 20:08:29-- https://get.jenkins.io/plugins/kubernetes-plugin
Resolving get.jenkins.io (get.jenkins.io)... 52.167.253.43
Connecting to get.jenkins.io (get.jenkins.io)|52.167.253.43|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-05-17 20:08:31 ERROR 404: Not Found.

wget https://get.jenkins.io/plugins -v
--2021-05-17 20:08:57-- https://get.jenkins.io/plugins
Resolving get.jenkins.io (get.jenkins.io)... 52.167.253.43
Connecting to get.jenkins.io (get.jenkins.io)|52.167.253.43|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://get.jenkins.io/plugins/ [following]
URL transformed to HTTPS due to an HSTS policy
--2021-05-17 20:08:58-- https://get.jenkins.io/plugins/
Reusing existing connection to get.jenkins.io:443.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘plugins’

plugins [ <=> ] 245.79K 149KB/s in 1.6s

2021-05-17 20:09:37 (149 KB/s) - ‘plugins’ saved [251684]

2 replies
yr-sudhakar
@yr-sudhakar
Plugin Install Manager page to be inserted in the vicinity of "Managing Plugins"section of Jenkins User Book is posted for review @ https://groups.google.com/d/msgid/jenkinsci-docs/836c6ffa-c02f-4fba-964a-79c9a4638c4bn%40googlegroups.com?utm_medium=email&utm_source=footer
hp77
@hp77-creator
@timja you closed jenkinsci/plugin-installation-manager-tool#10 but there is this jenkinsci/plugin-installation-manager-tool#263 which we have to solve right? Should I create a new PR for jenkinsci/plugin-installation-manager-tool#263 ?
Tim Jacomb
@timja
yes sure @hp77-creator it was closed because of lots of conflicts and no activity
yr-sudhakar
@yr-sudhakar
Hi @oleg-nenashevm,
Thanks for assigning you and @timja as reviewers. I intended to do the same. Maybe I do not have the aurthority to do the same, since I did not find any obvious way to assign when I was creating the JIRA issue.
4 replies
@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.
Tim Jacomb
@timja
scripts do not have a suffix of -script
so no -1
Oleg Nenashev
@oleg-nenashev
@yr-sudhakar Hi, thanks for working on that! I agree with @timja
yr-sudhakar
@yr-sudhakar
@MarkEWaite As part of the tool user guide review, you indicated that the plugin manager tool does not function as expected in some cases. If you can be specific, I can see if it impacts the content of the document.
@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.
holmesb
@holmesb

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?

Tim Jacomb
@timja
you need to override JENKINS_UC_DOWNLOAD if you want to change the download url, the update center includes download links which will be pointing to get.jenkins.io
what are you trying to achieve though? you have some weird proxy that doesn't work with ssl?
holmesb
@holmesb
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...
Tim Jacomb
@timja
yes that's what I would suggest doing instead, you can just build a custom docker image is the easiest solution which includes your company cert
Neil H Watson
@neilhwatson
Question about the plugin manager. When I run this command on a fresh Jenkins install, I see plugins being downloaded, but after I see no plugins installed in the UI
        java -jar /usr/share/jenkins/jenkins-plugin-manager.jar \
          --plugin-file /usr/share/jenkins/plugins.txt
Graeme Wilson
@techlunacy
@neilhwatson you need to restart jenkins after the installation. maybe you could get away with a reload? or are you running before it starts?
Pasha
@pashcan
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 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
CocoVicky
@CocoVicky
image.png
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
Mark
@MarkRx
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.
Tim Jacomb
@timja
@MarkRx it's not 2.289.2 it's showing you the recommended version for your release line
Mark
@MarkRx

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
Mark
@MarkRx
This appears to have broke with 2.6.0. It works when using 2.5.0.
Mark Waite
@MarkEWaite
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
Mark
@MarkRx
I still want transitive undeclared dependencies to be latest. I think If the plugins are pinned then my pin should be used. If that results in a conflict it should fail.