| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
'git show-ref' returns multiple results where there are partial matches
for the given ref, which creates the possibility that we might resolve
a ref incorrectly. 'git rev-list' is also overkill for verifying that a
SHA1 is valid.
|
|
|
|
|
|
|
|
| |
This bug has been present since the initial commit to the cache
server. Due to the missing repo_dir argument to rev_list(), resolving
SHA1s rather than symbolic refs via /1.0/sha1s fails. This feature,
however, is absolutely required for morph to resolve petrified system
branches.
|
| |
|
|
|
|
|
|
|
|
| |
Morph now expects the tree SHA1 in addition when resolving references
using the cache server. This is to better facilitate correct cache
key computation since commits can be made which have no tree changes
and thus nothing to usefully affect the build. (For example the morph
branch and build features)
|
|
|
|
|
|
|
| |
Direct-mode, when enabled, causes morph-cache-server to assume a more
Trove-like structure for the repositories, rather than the morph-cache
structure which it was originally written for. This means that for
the workers, we can use the original code and for Trove, the direct mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/trees queries take repo URI, a SHA1 ref and an optional path parameter.
The result is a JSON dictionary of the form
{
"repo": "<repo URI>",
"ref": "<SHA1 ref>",
"tree": {
"filename1": {
"mode": "100644",
"kind": "blob",
"sha1": "FOOBARBAZ"
},
...
}
}
|
| |
|
| |
|
| |
|
|
|