Commit Graph

17 Commits (00dcf0f1acafb7f5f5939f25bb7eb868d151fb1f)

Author SHA1 Message Date
James Tanner b98ab745f1 fix docstring indentation on scc modules 11 years ago
Skylar Saveland 5243bd5fa3 executable option to git module 11 years ago
James Cammarata 7bd8c18fa7 Merge branch 'gitfix' of https://github.com/johanwiren/ansible into johanwiren-gitfix 11 years ago
Johan Wirén dcd556b92f Fixed so that we no longer check with the remote if a checkout already is at the desired sha version. 11 years ago
Drew Blas 9ede377380 Added git disclaimer about dealing with ssh host checking
This disclaimer already exists in library/source_control/hg but not here.  It affects both and was discussed awhile back on: https://groups.google.com/forum/#!msg/ansible-project/q9G9xIdsRxo/XJhQzuS-qSoJ  However no PR was ever sent to fix the doc.
11 years ago
Petr Svoboda d9576b3529 Tidy up fix of git module traceback 11 years ago
Petr Svoboda 2d5b942ffe Fix traceback in git module when version checkout fails
"UnboundLocalError: local variable 'branch' referenced before assignment" is
raised in git, line 282, in switch_version.

Exception is raised when version is not branch and version checkout fails.
E.g. when version is nonexistant commit.
11 years ago
Michael DeHaan 32d5038d72 Don't add --version HEAD parameter is already HEAD, some versions of git don't like this. 12 years ago
James Laska 95a22338a2 Resolve incompatability between depth and version
Git is unable to checkout the specified `version` when the repository is
cloned with a reduced history (`depth`).  However, if the repository is
already cloned, subsequent git module calls will update the repository
(default update=True), then properly checkout the specified `version`.
To allow the initial call to properly clone the specified `version`, at
the specified `depth`, this patch adds the `--branch` parameter when
cloning the repository.
12 years ago
Matt Spaulding 871f781ec7 Fix git submodule update when version specified 12 years ago
Stephen Fromm 76d848331f Add submodule support to git module
This does two things:
* add --recursive option to git clone command in clone().  This will
  initialize all submodules when cloning a remote repository.
* Add submodule_update() and call that from fetch().  submodule_update()
  calls two git commands iff the file .gitmodules exists in the
  repository:
  * 'git submodule sync' - synchronizes the submodules' remote URL
    configuration setting to the value in .gitmodules.
  * 'git submodule update --init --recursive' - initialize and update
    registered submodules to the commit specified in the index of the
    containing repository.

If a repository was cloned without --recursive, submodule_update() will
ensure that the submodules are initialized and updated.
12 years ago
Jan-Piet Mens 5c69918d53 DOCS: standardize on EXAMPLES (a.k.a. Docs-JumboPatch JetLag Edition)
Migrated all examples: in DOCUMENTATION=''' string to standalone EXAMPLES=''' string
  Added deprecation warning to moduledev.rst and remove deprecated example from it
  Fixed up a few typos and uppercased some acronyms.
  add consistency to how EXAMPLES are formatted
12 years ago
Benjamin Schwarze a0c89e742e remove unused git function is_current_branch (looks like it returns always True anyway which might be wrong) 12 years ago
Benjamin Schwarze 3cae9d6d0d use module.get_bin_path('git', True) once and pass git_path to functions 12 years ago
Stoned Elipot c9f268ac48 Fix typo in git module documentation preventing it to be processed by ansible-doc 12 years ago
Jesse Keating f645d27f5e Add an update option to the git module
This will allow just making sure the repo exists w/out actually making
any chnages to it. Useful if you're going to run a play repeatedly
against a host that might have active development going on in the
repository (think initial bootstrap of a developers system, and
continued playbook runs to work on other projects).
12 years ago
Michael DeHaan 391fb98ee2 Allow modules to be categorized, and also sort them when generating the documentation. 12 years ago