Puppet module to manage VCS repositories
Go to file
Steve Kowalik 285f114087 Remove spec directory
This directory is full of code that's rotten or rotting, delete it
and the horse it rode in on.

Change-Id: If27065124e6cc900d9bb000b651ca48a77df6d33
2015-05-22 08:33:19 +10:00
examples Make Puppet DSL compliant with the style guides and puppet lint. 2012-03-11 21:10:08 +00:00
lib/puppet Checkout local revision if not tag/remote branch. 2012-12-21 01:08:02 +00:00
.gitignore Add .gitignore 2010-03-13 14:02:55 -08:00
.gitreview Updated .gitreview location 2012-12-17 18:53:08 +00:00
LICENSE Add GPL license (from Puppet core) 2010-03-14 03:24:15 -07:00
Modulefile Rename openstackci to openstackinfra 2015-04-20 13:51:45 -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 (#13062) Added clarification that 'revision' can also be used for branches. 2012-04-05 14:54:40 +01: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.