Puppet module to manage VCS repositories
Go to file
Matt Robinson b931190b32 (#11798) Fix git checkout of revisions
The git provider had some problems checking out SHA1s - it couldn't.
And what's worse, it lied about what it was doing saying that it did
checkout the SHA1.

There was also a bug where if you specified a different branch than you
were on, it was doing a `reset --hard` to the specified branch.  For
example, if master was checked out, and you set "revision => stable", it
would `git reset --hard stable` on the master branch instead of just
checking out stable.  Maybe the original author did this to get around
being unable to checkout when you had local changes, but the --force
flag to checkout will fix that.

With this change, you should now be able to specify a branch, tag, or
SHA1 in the revision attribute and have it work.
2012-01-19 15:20:40 -08:00
examples Working Bazaar support & docs 2010-03-14 01:19:13 -08:00
lib/puppet (#11798) Fix git checkout of revisions 2012-01-19 15:20:40 -08:00
spec Support different create and revision= operations depending on the revision type in Git (commit, tag, or local/remote branch) 2010-03-18 14:46:12 -07:00
.gitignore Add .gitignore 2010-03-13 14:02:55 -08:00
LICENSE Add GPL license (from Puppet core) 2010-03-14 03:24:15 -07:00
Modulefile Incremented version 2011-09-21 11:10:10 -07:00
README.BZR.markdown Tweak markup 2010-03-14 03:08:03 -07:00
README.CVS.markdown Add pointer for Puppet SSH approach 2010-03-14 03:00:37 -07:00
README.GIT.markdown Add pointer for Puppet SSH approach 2010-03-14 03:00:37 -07:00
README.HG.markdown Tweak markup 2010-03-14 03:08:03 -07:00
README.SVN.markdown Add pointer for Puppet SSH approach 2010-03-14 03:00:37 -07:00
README.markdown Convert bare repos to working copy repos and vice-versa 2010-03-13 00:00:11 -08:00
Rakefile Add Rakefile for the non-autotest inclined 2010-03-13 12:18:00 -08:00

README.markdown

vcsrepo

Purpose

This provides a single type, vcsrepo.

This type can be used to describe:

  • A working copy checked out from a (remote or local) source, at an arbitrary revision
  • A "blank" working copy not associated with a source (when it makes sense for the VCS being used)
  • A "blank" central repository (when the distinction makes sense for the VCS being used)

Supported Version Control Systems

This module supports a wide range of VCS types, each represented by a separate provider.

For information on how to use this module with a specific VCS, see README.<VCS>.markdown.

License

See LICENSE.