Puppet module to manage VCS repositories
44eb9ad8f7
ensure => latest should work and trigger when the remote has new revs, and not at other times. It will handle tags and branches apparently and will also handle not specifying a branch in the revision. |
||
---|---|---|
examples | ||
lib/puppet | ||
spec | ||
.gitignore | ||
LICENSE | ||
Modulefile | ||
Rakefile | ||
README.BZR.markdown | ||
README.CVS.markdown | ||
README.GIT.markdown | ||
README.HG.markdown | ||
README.markdown | ||
README.SVN.markdown |
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/