Confirmed users
142
edits
ReleaseEngineering/Applications/Mapper: Difference between revisions
ReleaseEngineering/Applications/Mapper (view source)
Revision as of 18:43, 30 May 2014
, 30 May 2014→What is it?
| Line 7: | Line 7: | ||
Mapper is a rest api, that allows: | Mapper is a rest api, that allows: | ||
# insertion of new mappings and projects (a "project" is essentially the name of the repo - e.g. build-tools) (HTTP POST) | |||
# insertion of git/hg mappings for a given project (HTTP POST) | |||
# retrieval of mappings for a given project (HTTP GET) | |||
Behind the scenes, it is reading/writing from the database (using sqlalchemy). | Behind the scenes, it is reading/writing from the database (using sqlalchemy). | ||
| Line 15: | Line 15: | ||
Note: the vcs sync tool is a client of the mapper: it is vcs sync that inserts into mapper (i.e. uses the HTTP POST methods). | Note: the vcs sync tool is a client of the mapper: it is vcs sync that inserts into mapper (i.e. uses the HTTP POST methods). | ||
The other clients of mapper will be: | The other clients of mapper will be: | ||
# people / developers - wanting to query mappings | |||
# b2g_build.py - the build script for b2g - since this needs to lookup shas in order to reference frozen commit versions in manifests | |||
Mapper is written as a RelEng API blueprint - please note RelEng API has its own documentation too. | Mapper is written as a RelEng API blueprint - please note RelEng API has its own documentation too. | ||