Skip to content

Commit

Permalink
Document the known bug with "ensure => 'latest'" for jenkins::plugin
Browse files Browse the repository at this point in the history
This should close voxpupuli#98, but ultimately be fixed in Duckworth
  • Loading branch information
R. Tyler Croy committed Feb 26, 2014
1 parent 4b62385 commit cc8d1d8
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions README.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -31,12 +31,18 @@ The names of the plugins can be found on the [update
site](http://updates.jenkins-ci.org/download/plugins)

#### Latest

By default, the resource will install the latest plugin, i.e.:

jenkins::plugin {
"git" : ;
}

If you specify `version => 'latest'` in current releases of the module, the
plugin will be downloaded and installed with *every* run of Puppet. This is a
known issue and will be addressed in future releases. For now it is recommended
that you pin plugin versions when using the `jenkins::plugin` type.

#### By version
If you need to peg a specific version, simply specify that as a string, i.e.:

Expand Down

0 comments on commit cc8d1d8

Please sign in to comment.