Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Ewelina Wilkosz
@ewelinawilkosz
thanks! :)
Oleg Nenashev
@oleg-nenashev

Hi @timja @jetersen I am currently looking at https://github.com/jenkinsci/plugin-installation-manager-tool/pull/94/files#r426277438 and thinking whether I could revert it so that it becomes possible to install plugins into a non-empty directory. The code is quite messy there, but I see the following flow:

  1. Cleaning the target plugin directory becomes an opt-in flag
  2. Plugin Installation Manager downloads all plugins into a temporary directory, in parallel
  3. Plugin Installation Manager gradually moves plugins from a temporary directory, while skipping plugins which are already there and have higher versions

It would also re-enable the --list command

WDYT?

The code is very hairy there, so I am not 100% sure it is going to fly
Tim Jacomb
@timja
the --list command didn't do anything that useful imo ?
it just listed plugins it was going to install
it didn't list plugins already installed
it's fine to remove the deletion that was only a temporary fix because of the checksum work
Oleg Nenashev
@oleg-nenashev
OK. I will just try to clean removal to see how it fares. If there are issues, will consider moving files through a temporary directory. It does not look necessary, because the download resolution logic happens before we actually start downloads
Oleg Nenashev
@oleg-nenashev
I will cut the https://github.com/jenkinsci/plugin-installation-manager-tool release, OK? Do not want to sit on these patches
Tim Jacomb
@timja
go for it
feel free to release after any PR
don't need to ask
i tend to merge a PR and if anything else is ready merge it otherwise just release straight away
Oleg Nenashev
@oleg-nenashev
Makes total sense
Oleg Nenashev
@oleg-nenashev
Had to re-spin the GitHub release to fix artifacts
Tim Jacomb
@timja
ha i did get hit by a 404 :p
Jerry
@solvingj
first time using plugin. trying FROM jenkins/jenkins:2.263.1-lts. All plugin installs failing, when i turn on verbose i get: "Unable to resolve plugin URL https://updates.jenkins.io/download/plugins/workflow-job/2.40/workflow-job.hpi, or download plugin workflow-job to file"
any obvious common cause for this?
Jerry
@solvingj
well i thought it might be something with debian certificates or ssl, so i just switched to the centos image and get the same result. here's my dockerfile if anyone wants to try building it. maybe something with my containers network access and my firewall (docker-for-windows)? I dunno, but this should be simple i think. https://gist.github.com/solvingj/6a9dbcea540d43ff2342776a52844714
Jerry
@solvingj
yikes, works on my other laptop :(
thanks all
Tim Jacomb
@timja
You have a proxy?
Jerry
@solvingj
no proxy
solved it, the corporate software suite included an additional firewall i was not aware of :(
i disabled one firewall... but it was the classic "second firewall"
weird that all the other internet-related operations don't suffer
wgets and curls and stuff to other places
hp77
@hp77-creator
How do I run tests on plugin-installation-manager-tool locally on my machines, I am trying to run jenkins instance on docker
Mark Waite
@MarkEWaite
I run those tests with the command mvn clean verify. You could also use the command mvn clean test.
16 replies
gulshanpahuja77
@gulshanpahuja77
Hi All, I have one Linux server on which Internet is not working and I have installed Jenkins in offline mode..Now I need to install plug-ins ..I know that if I open Plug-ins manager in Jenkins UI -> Advanced tab then there is option to install plug-in one by one providing .hpi file (downloaded on Windows machine as I have internet working on windows machine)...But this process is very time consuming as I need to down load dependencies one by one...Can any one please suggest that how can I install all required plug-ins by using some shorter method
1 reply
Chitrank Dixit
@Chitrank-Dixit

Hi Guys,

I am following Jenkins tutorial (https://www.jenkins.io/doc/book/installing/kubernetes/) to deploy jenkins to kubernetes for CI/CD work as we are planning to use jenkins for CI/CD. But the pod fails to start due to the issue with update center and shows the error

disable Setup Wizard download plugins Error getting update center json

Do I need to specify different source for plugin update center somewhere in my jenkins-values.json (as specified in the tutorial above)
Mark Waite
@MarkEWaite
@Chitrank-Dixit if you're receiving a message that the update center is unavailable, that likely means your Kubernetes cluster does not have access to the public internet. If it does not have access to the public internet and it is intentionally not allowed to access the public internet, then you need to perform an offline installation by creating a Docker image that contains all the plugins you need and uploading that Docker image to a container registry that is accessible to the Kubernetes cluster. Refer to https://www.jenkins.io/doc/book/installing/offline/ for hints on offline installation
Mark Waite
@MarkEWaite
Failed access to the update center should not fail pod startup. Failure to download plugins from the plugin installation manager scripts inside the Docker container probably will fail pod startup. Use the plugin installation manager in a Docker container to define your own container and run that container. That's the technique used in the Docker installation instructions at https://www.jenkins.io/doc/book/installing/docker/#on-macos-and-linux and in the build tools tutorials at https://www.jenkins.io/doc/tutorials/#tools
SlotOne
@slotone
hello everyone
I've installed a few plugins through plugin-manager-tool, and they show as installed when executing with --list option
however they are not displayed in the Web UI
what I'm doing wrong ?
have to mention I'm testing this on a ubuntu instance, no docker image
Tim Jacomb
@timja
plugin manager tool doesn't interact with jenkins at all except to get the jenkins version,
so I would guess you've put the plugins in the wrong folder @slotone
i.e. --list doesn't actually mean it's installed to jenkins
SlotOne
@slotone
Thanks Tim, I've not specified the folder, in order to use default location
will try specifying it
Tim Jacomb
@timja
the default location assumes a docker image
SlotOne
@slotone
ahh ok
NilmaPeiris
@NilmaPeiris
Hello everyone I'm Nilma, a 2nd year undergraduate. I hope to continue my GSOC 2021 journey with Jenkins and I went through all the GSoC 2021 project ideas and I would like to work on this project.
Mark Waite
@MarkEWaite
That's great @NilmaPeiris . Looking forward to your questions