summaryrefslogtreecommitdiff
path: root/spec/unit
AgeCommit message (Collapse)Author
2014-01-11git: actually use the remote parameterMiguel Di Ciurcio Filho
When using the following sample, the provider does not use the value of remote when cloning a repository: vcsrepo {'/path/to/repo': ensure => 'present', provider => 'git', remote => 'test', source => 'git@somerepo:repo.git', } $ git remote origin This commit makes sure that the new repository has a remote with the supplied value. Closes #MODULES-430
2014-01-07Add the option to shallow clones with gitFelipe Reyes
The new parameter used to indicate that you want a shallow clone is `:depth`
2013-12-04Stripping git on_branch? return value; contains trailing newlineMike Gerwitz
This commit also contains git provider `latest' method formatting changes; squashed by request.
2013-12-02Using rev-parse to determine branch name of HEAD for on_branch? methodMike Gerwitz
2013-09-18Add convert_working_copy_to_bear and convert_bare_to_working_copy tests.Ashley Penney
2013-09-18Add tests for convert_working_copy_to_bare andAshley Penney
convert_bare_to_working_copy
2013-09-18Add latest tests.Ashley Penney
2013-09-18Add test for latest?Ashley Penney
Also add some fixtures for previous tests.
2013-09-18Overhaul the spec tests to work in rspec2.Ashley Penney
This work gets rid of the provider_example_group and reworks everything to work properly against rspec2. I don't know if I'd consider the style "better" but it works.
2013-08-28update git provider to handle checking out into an existing (empty) dirJohn Iacona
2013-08-12And fix the rspec test to pass.Michael Arnold
2013-07-25Handle revision update without source switch.Aaron Stone
2013-07-25Update specs for svn switchAaron Stone
2013-07-19Add support for master svn repositories5Ub-Z3r0
Pull request related to issue #8331. I have added support into the exists? method (actually working_copy_exists?) for checking if the path is a master repository, using svnlook. It should be ok in most cases, since svnlook comes with svnadmin in nearly every distribution.
2013-07-17Merge pull request #46 from Paulche/masterAaron Stone
Enable unlimited nesting for submodule updating
2013-07-17fix git provider checkout of a remote ref on an existing repoJoshua Hoblitt
Per discussion of https://github.com/puppetlabs/puppetlabs-vcsrepo/issues/51 in the git channel on freenode, EugeneKay <eugene@kashpureff.org> stated that `git rev-parse` is not capable of inspecting remote refs but that `git ls-remote` is. This patch makes a second attempt to resolve the ref with `ls-remote` if `rev-parse` fails. The git provider also appears to support several type features that are not tagged under `has_features`. It's not clear if this is the best way to resolve this issue or if the provider should be refactored to work with different type features. Demonstration of the problem with changing refs (branches and tags) $ git --version git version 1.7.1 $ cat master.pp branch.pp vcsrepo { '/tmp/vcsrepo': ensure => present, provider => git, source => 'https://github.com/puppetlabs/puppetlabs-vcsrepo.git', revision => 'master', } vcsrepo { '/tmp/vcsrepo': ensure => present, provider => git, source => 'https://github.com/puppetlabs/puppetlabs-vcsrepo.git', revision => 'feature/cvs', } $ puppet apply --modulepath=`pwd`/.. master.pp Notice: /Stage[main]//Vcsrepo[/tmp/vcsrepo]/ensure: Creating repository from present Notice: /Stage[main]//Vcsrepo[/tmp/vcsrepo]/ensure: created Notice: Finished catalog run in 2.19 seconds $ puppet apply --modulepath=`pwd`/.. branch.pp Error: /Stage[main]//Vcsrepo[/tmp/vcsrepo]: Could not evaluate: Execution of '/usr/bin/git rev-parse feature/cvs' returned 128: fatal: ambiguous argument 'feature/cvs': unknown revision or path not in the working tree. Use '--' to separate paths from revisions feature/cvs Notice: Finished catalog run in 1.69 seconds
2013-07-17Unlimited sudmodule's nesting for git providerPaul Chechetin
2013-07-14Fix bzr specs broken for a whileAaron Stone
2013-07-14Fix git tests broken by dcd0d14Aaron Stone
2013-03-06Update origin if necessary before checking revisionRaphaël Pinson
2012-10-19Dummy provider raises an exception if it is used. Tests to prove it.Aaron Stone
2012-10-19Use symbols consistently with provider.expects()Aaron Stone
2012-10-18Remove excess whitespace.Aaron Stone
2012-10-18Update tests to match current code.Aaron Stone
2012-10-18Get the specs running under bundler.Aaron Stone
2012-05-02Fix failing hg provider spec caused by refactoring in commit ↵John Chilton
f1120f2d9b121097b7e77709328144af330d0b34
2010-03-18Support different create and revision= operations depending on the revision ↵Bruce Williams
type in Git (commit, tag, or local/remote branch)
2010-03-18Add submodule support to git providerBruce Williams
2010-03-18Move support fileBruce Williams
2010-03-18Fix bad context nestingBruce Williams
2010-03-18Rename methods context_with(out)? => context_with\1_resource for clarityBruce Williams
2010-03-18Subversion to use provider example group API for specsBruce Williams
2010-03-18Mercurial to use provider example group API for specsBruce Williams
2010-03-18CVS uses provider example group for specsBruce Williams
2010-03-17Further condense provider example group API, update Bazaar provider spec to ↵Bruce Williams
use it.
2010-03-17Build ProviderExampleGroup for refactored provider testsBruce Williams
2010-03-15ensure = latest to support reference tracking.\n\nWorking with tags, more ↵Bruce Williams
work needed for branches (at least with git)
2010-03-14Basic Bazaar supportBruce Williams
2010-03-13Support Mercurial tags, restructure examplesBruce Williams
2010-03-13Basic Mercurial supportBruce Williams
2010-03-13Basic CVS supportBruce Williams
2010-03-13Some fixes after live testing, add support for bare cloned reposBruce Williams
2010-03-13Convert bare repos to working copy repos and vice-versaBruce Williams
2010-03-12Tests for Git revision property, cleanupBruce Williams
2010-03-12Basic SVN providerBruce Williams
2010-03-12Basic tests for git provider, stub for svn providerBruce Williams