jenkins version in jenkins charm

[Mark Shuttleworth]

On 10/01/14 14:56, Richard Harding wrote:
> 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.

That's unusual behaviour - IIRC most charms that let you set a version,
take care of fetching, installing and *using* that version. Definitely
sounds like the charm is missing that logic.

Mark