Go to file
mikeknox dd31bce565 When ensure => latest, svn didn't update.
svn provider now gets the latest revision from the repo, rather than the checkout
Test with revision => <some value> as well

now when ensure => latest, only refresh dependent resources if the
repo is actually updated

Tidied up debug messages
2010-07-22 09:19:38 +10:00
2010-03-14 01:19:13 -08:00
2010-03-13 14:02:55 -08:00
2010-03-14 03:24:15 -07:00
2010-06-24 18:22:24 +10:00
2010-03-14 03:08:03 -07:00
2010-03-14 03:08:03 -07:00

Using vcsrepo with Subversion

To create a blank repository

To create a blank repository suitable for use as a central repository, define a vcsrepo without a source or revision:

vcsrepo { "/path/to/repo":
  ensure   => present,
  provider => svn
}

To checkout from a repository

Provide a source qualified to the branch/tag you want:

vcsrepo { "/path/to/repo":
    ensure   => present,
    provider => svn,
    source   => "svn://svnrepo/hello/branches/foo"
}

You can provide a specific revision:

vcsrepo { "/path/to/repo":
    ensure   => present,
    provider => svn,
    source   => "svn://svnrepo/hello/branches/foo",
    revision => '1234'
}

For sources that use SSH (eg, svn+ssh://...)

Manage your SSH keys with Puppet and use require in your vcsrepo to ensure they are present. For more information, see the require metaparameter documentation1.

More Examples

For examples you can run, see examples/svn/

Description
Puppet module to manage VCS repositories
Readme 270 KiB
Languages
Ruby 100%