example42/puppet-jenkins — pull request #3 by mrolli (2012-11-13 16:47:24+00:00)
Title: Make the plugin manifest actually work, with limitiations (depends on Se...

The plugin manifest in its current form didn't work for as you stated in the comment. Not knowing to what you would like to adopt it I enhanced it to serve at least my current scenario. Having played with jenkins-cli I returned to wget. So, the plugin now:

* installs the latest or a specific version of a plugin
* unless its already installed
* general purpose is initial provisioning of a jenkins server
* fails actively if Service['jenkins'] is not defined
* handles hpi vs. jpi situation (when jenkins webapp was used to update/install)

Known limitations:

* does only work with jenkins::params::install = package due to
* dependency on /var/lib/jenkins/plugins (in tomcat the plugin_dir seems to elsewhere)
* dependency on Service['jenkins']
* does not compare to be installed version of a plugin with already installed version => not autoupdates of plugins

For me the current state is useful in daily business, plugin comparison and autoupdate (to specific or latest version ) of plugins would be nice to have, but more work.

Tested with vagrant/Ubuntu 12.04.1 LTS only.