On Fri, 10 Jan 2014, Steve Powell wrote: > I have deployed the jenkins charm (and slaves) successfully, but cannot > get the right version of jenkins installed that permits me to install the > right plugins. > > Here are my settings: > > ... > and I have tried release distro, trunk and lts, and they all remaining > stuck on the same release. The plugins (git maven-plugin > parameterized-trigger) are all accepted (and the hook completes > successfully) but only the last one is actually installed (apparently) > because the others are too up-level to work with the (old) release of > jenkins. > > I can download a jenkins.war of a later release, but how do I tell the > charm to use it? > > Is it time for me to ‘get down and dirty’ with the charm implementation? > > Steve Powell
Steve, I believe that changing the release changes the source updates are fetched from during the normal apt-get install/upgrade process. It does not actually perform the upgrade itself. I also run a Jenkins install from the charm and have it running with the release set to 'trunk'. Even with this set, all it does is add the apt repository from Jenkins to the server. Updates need to be managed. A tool like Landscape [1] can be used to manage the updates on the system. You should be able to ssh to the machine and perform an apt-get update && apt-get upgrade to get the Jenkins package to update. If you do want to get dirty with the charm implementation the work that handles the release updates is part of the install hook in the charm [2]. You can find the source for it here [3] and see that it's just doing an apt-get install. Not an upgrade. 1: http://www.ubuntu.com/management/landscape-features 2. https://jujucharms.com/precise/jenkins/ 3. http://bazaar.launchpad.net/~charmers/charms/precise/jenkins/trunk/view/head:/hooks/install#L15 -- Rick Harding Cloud Engineering https://launchpad.net/~rharding @mitechie -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
