Increase Jenkins version and use plugin installation manager tool

[reinholdfuereder]

(Newer "jenkins/jenkins" Docker base images already contain v2.1.0 of plugin installation manager tool)

[oleg-nenashev]

--war option needs to be passed so that the tool consults with version compatibility requirements

[reinholdfuereder]

Thanks for the hint!

However, after consulting the documentation:

--war or -w: (optional) Path to Jenkins war file. If no war file is entered, will default to /usr/share/jenkins/jenkins.war or C:\ProgramData\Jenkins\jenkins.war, depending on the user's OS.

... and inspecting the Docker container:

docker run -it --rm --name jenkins -e DEV_HOST=10.1.114.226 -p 8080:8080 -p 50000:50000 xortex/jenkins:0.2 /bin/bash
jenkins@52ea5cf6e190:/$ ls -la /usr/share/jenkins/jenkins.war
-rw-r--r-- 1 root root 67242720 Oct 20 14:57 /usr/share/jenkins/jenkins.war

... I think this is not necessary (anymore?), because the default should be sufficient, shouldn't it?

[reinholdfuereder]

Oh wow, today we extremely often get also failures during downloading of plugins! So maybe your comment in 1c081df#commitcomment-43409028 also applys for the downloading feature! ;-(
=> we have now switched back to the old (deprecated) tool... not sure if that is the real solution though... because the mirror server is also under seemingly consistently higher load (cf. bottom of http://mirror.serverion.com/)!?

But it looks like the error handling is also "not at all perfect" (little understatement) in the new tool!?

Failure example (note that is always a different plugin):

...
maven-plugin downloaded successfully
Unable to download blueocean-personalization
ERROR: Service 'jenkins' failed to build: The command '/bin/sh -c jenkins-plugin-cli --plugin-file /usr/share/jenkins/ref/plugins.txt' returned a non-zero code: 1