jenkins version in jenkins charm

[Steve Powell]

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:

$ juju get jenkins
charm: jenkins
service: jenkins
settings:
  password:
    description: Admin user password - used to manage slave nodes so please don't
      change in Jenkins.
    type: string
    value: […]
  plugins:
    description: Space separated list of plugins to install
    type: string
    value: git maven-plugin parameterized-trigger
  plugins-check-certificate:
    default: true
    description: Set to no to allow downloading from an invalid https site.
    type: string
    value: "yes"
  plugins-site:
    default: true
    description: Site to download plugin .hpi files from.
    type: string
    value: https://updates.jenkins-ci.org/
  release:
    description: "Source of Jenkins, options include:\n- distro: only use the Ubuntu
      distribution - this\n  is the default and only works on >= Oneiric.\n- lts:
      use the most recent Jenkins LTS release.\n- trunk: use the most recent Jenkins
      release.\n"
    type: string
    value: trunk
  remove-unlisted-plugins:
    default: true
    description: 'Set this to yes to remove any plugins not listed in plugins
      from the installation.
'
    type: string
    value: "no"
  tools:
    default: true
    description: Tooling to deploy alongside jenkins
    type: string
    value: git gcc make bzr
  username:
    default: true
    description: Admin user username - used to manage slave nodes so please don't
      change in Jenkins.
    type: string
    value: admin

(which helpfully explains them — is there a way to get these explanations directly from the charm?)

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140110/53bc1754/attachment.html>