Please make the Jenkins installer use a _STATIC_ package
|Assignee:||Johannes Wienke||% Done:|
|Category:||Recipe||Spent time:||9.66 hours|
|Target version:||Toolkit 0.1|
Today I wanted to convince a colleague to make use of the new tool chain, aka toolkit-distribution using recipes via local Jenkins, instead of the Gar-Installer (which my colleague is used to and which he really likes) to distribute his components. After explaining him the advantages of the "new" approach he was willing to try it.
Again, the Jenkins bootstrapping failed because some plugins couldn't be fetched (Git, Build-Flow), which I only found out by checking the Jenkins config via Jenkins GUI. Comment of the the colleague:
"Okay, at this point I would already be lost..."
Additionally, somehow Jenkins is not able to find the Plugin repository (Jenkins version is: Jenkins ver. 1.532.2) so I really wasn't able to create all Jobs because the build-generator fails, again, because Jenkins was not setup correctly.
IMHO this is basically A SHOW STOPPER we will not be able to convince people to use our new tool chain (I am fully convinced it's the right way to go) if the setup already fails, especially because Jenkins is such a central component.
I really don't blame the implementation/developer of the installer script, dynamic web-based fetching of plugins is simply
a "fragile" thing.
I would like to vote for a hosted tar.gz file including all the required plugins and Jenkins itself.
Configure update site correctly
Despite using the LTS update site for first plugin installation, the one
configured inside jenkins was still pointing to the trunk plugins. This
commit also configures the URL for the LTS plugins.
Make installed folder relocatable
Removed the absolute location from the starter script.
Fail in case a plugin could not be installed
In some cases the jenkins CLI does not indicate an error if a plugin
could not be installed. In order to still catch those error, actively
check for the each new plugin being installed.
#2 Updated by Arne Nordmann over 6 years ago
- Status changed from New to Feedback
I kind of agree, this still feels fragile (well, it is some kind of prototype). I managed to use by just re-doing it one or two times and then the plugin installation went well. At some point I installed the required plugins by myself ... but I agree, this is not very usable and a showstopper.
So if we could go for a archive with the latest Jenkins LTS and stable versions of the plugins, that would be very nice. I like the idea.
#18 Updated by Johannes Wienke over 6 years ago
- % Done changed from 0 to 90
A jenkins jobs is now available and installation has been fixed as much as possible. Can someone please test the archive before I add a description to the wiki page:
#19 Updated by Sebastian Wrede over 6 years ago
Nice. Does the static package already get pushed to some publicly available location?
https://ci.toolkit.cit-ec.de/job/jenkins-distribution/ is not available from outside of the university network (IIRC) or is otherwise currently not available (also not when connecting via VPN).
#26 Updated by Florian Lier over 6 years ago
Now, the CI generated *tar.gz is scp'ed on the toolkit machine and available via:
#27 Updated by Florian Lier over 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
The file is avail under: https://toolkit.cit-ec.uni-bielefeld.de/dist/jenkins.tar.gz