mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
39fa21c146
Summary: Infinitepush index implementation that uses mysql db to store data. Three tables: 1) Node to bundle 2) Bookmark to node 3) All bundles (this is necessary to find unused bundles. Test Plan: Code was tested but tests are not included in the diff - see comments below Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters Differential Revision: https://phabricator.intern.facebook.com/D3811247 Tasks: 12479677 Signature: t1:3811247:1473378520:bc23b3436aa2e618a7bfefd2d571257dfe8ace94 |
||
|---|---|---|
| .. | ||
| integrationtests | ||
| tests | ||
| __init__.py | ||
| indexapi.py | ||
| README | ||
| store.py | ||
## What is it?
This extension adds ability to save certain pushes to a remote blob store
as bundles and to serve commits from remote blob store.
The revisions are stored on disk or in everstore.
The metadata are stored in sql or on disk.
## Config options
infinitepush.branchpattern: pattern to detect a scratchbranch, example
're:scratch/.+'
infinitepush.indextype: disk or sql for the metadata
infinitepush.reponame: only relevant for sql metadata backend, reponame to put in
sql
infinitepush.indexpath: only relevant for ondisk metadata backend, the path to
store the index on disk. If not set will be under .hg
in a folder named filebundlestore
infinitepush.storepath: only relevant for ondisk metadata backend, the path to
store the bundles. If not set, it will be
.hg/filebundlestore