This helps us query information about Mozilla’s Mercurial repositories.
Documentation found in here: http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmo/pushlog.html
Important notes from the pushlog documentation:
When implementing agents that consume pushlog data, please keep in mind the following best practices: * Query by push ID, not by changeset or date. * Always specify a startID and endID. * Try to avoid full if possible. * Always use the latest format version. * Don't be afraid to ask for a new pushlog feature to make your life easier.
Return the full 40 chars revision number which correspond to the 12 chars revision number we given, and throw an error out if found collision in there.
- repo_url – The repo url of a repository e.g. mozilla-inbound
- revision (str) – push revision (40 chars)
query_pushid_range(repo_url, start_id, end_id, version=2)¶
Return an ordered list of revisions (newest push id first).
repo - represents the URL to clone a repo start_id - from which pushid to start with (oldest) end_id - from which pushid to end with (most recent) version - version of json-pushes to use (see docs)
Return the tip of a branch.
query_revision_info(repo_url, revision, full=False)¶
Return a dictionary with meta-data about a push including:
query_revisions_range(repo_url, from_revision, to_revision, version=2, tipsonly=1)¶
Return an ordered list of revisions (by date - oldest (starting) first).
repo - represents the URL to clone a repo from_revision - from which revision to start with (oldest) to_revision - from which revision to end with (newest) version - version of json-pushes to use (see docs)
query_revisions_range_from_revision_before_and_after(repo_url, revision, before, after)¶
Get the start and end revisions based on the number of revisions before and after.
Raises PushlogError if pushlog data cannot be retrieved.
Verify that a revision exists in a given branch.