Caches git repositories locally. Every time a build happens, it uses local caches for pulling. Submodules especially, which are harder to intercept for caching.
Will also inflate submodules recursively.
With 8 submodules, a total of 150MB of data to clone:
Before caching: 13.79s user 6.36s system 18% cpu 1:49.45 total
After caching: 2.12s user 2.07s system 25% cpu 16.310 total
Cached repositories are stored in ~/.git-cow by default. You can override this by setting $GIT_COW.
# Installation
Either:
with pypi: sudo pip install git-cachecow
Or:
Clone git-cachecow and add the directory to your $PATH.
# Usage
How to clone a repository with submodules:
git scclone git://github.com/grahamc/git-multi.git
## git-cclone git cclone repo_uri [clone_to [hash]]
## git-submodule-describe
Outputs submodule data into parsable format
` git://github.com/nationalfield/symfony.git lib/vendor/symfony aec67b5e7ba148c79b884b86988e42f9f9483bcd git@github.com:nationalfield/pheanstalk.git lib/vendor/pheanstalk 5b38924730b70ea720f760369899398479e2ea13 git@github.com:nationalfield/tinymce.git web/js/tiny_mce 0c3da0cc9e33df0f2b82f70bf7e24405de216bee `
- ## git-submodule-cclone
Clones all the submodules recursively at their defined location and hashes.
[](http://travis-ci.org/grahamc/git-cachecow)
1 maintainer
Metadata
1 maintainer
Release files for git-cachecow 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| git-cachecow-0.1.tar.gz | 3.4 kB | Without provenance | Details for git-cachecow-0.1.tar.gz |
Release files / git-cachecow-0.1.tar.gz
| Download URL | git-cachecow-0.1.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9cdfb75fa452166b7a03995e797f80791c30e8bbf07cba7ec51de608a71a616e
|
|
BLAKE2b-256 checksum How to use checksums |
ba8424440101140d678af674238f63764dd58af4f52a6ad35175ec451d85d29b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-cachecow 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
](http://travis-ci.org/grahamc/git-cachecow){kind=link}