buildgrid 0.0.86__tar.gz

buildgrid-0.0.86/BuildGrid.doap

@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Project xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+         xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+         xmlns:foaf="http://xmlns.com/foaf/0.1/"
+         xmlns="http://usefulinc.com/ns/doap#">
+
+  <name xml:lang="en">BuildGrid</name>
+  <shortdesc xml:lang="en">Remote execution service implementing Google's REAPI &amp; RWAPI</shortdesc>
+  <homepage rdf:resource="https://buildgrid.build" />
+  <mailing-list rdf:resource="https://lists.buildgrid.build/cgi-bin/mailman/listinfo/buildgrid" />
+  <download-page rdf:resource="https://gitlab.com/BuildGrid/buildgrid" />
+  <bug-database rdf:resource="https://gitlab.com/BuildGrid/buildgrid/issues" />
+
+  <programming-language>python3</programming-language>
+
+  <maintainer>
+    <foaf:Person>
+      <foaf:name>Distributed Build Team</foaf:name>
+      <foaf:mbox rdf:resource="mailto:dbuild@bloomberg.net" />
+    </foaf:Person>
+  </maintainer>
+</Project>

buildgrid-0.0.86/CONTRIBUTING.rst

@@ -0,0 +1,253 @@
+.. _contributing:
+
+Contributing
+============
+
+Some guidelines for people wanting to contribute. Also please always feel free
+to speak to us, we're very friendly :-)
+
+
+.. _feature-additions:
+
+Feature additions
+-----------------
+
+We welcome contributions in the form of bug fixes or feature additions. Please
+discuss with us before submitting anything, as we may well have some important
+context which will could help guide your efforts.
+
+Any major feature additions should be raised first as a proposal on the
+BuildGrid mailing list to be discussed between the core contributors. Once 
+this discussion has taken place and there is agreement on how to proceed, 
+it should be followed by with a Gitlab issue being raised which summarizes 
+the tasks required.
+
+We strongly recommend that you propose the feature in advance of
+commencing any work.
+
+The author of any patch is expected to take ownership of that code and is to
+support it for a reasonable time-frame. This means addressing any unforeseen
+side effects and quirks the feature may have introduced.
+
+.. _BuildGrid mailing list: https://lists.buildgrid.build/cgi-bin/mailman/listinfo/buildgrid
+
+.. _patch-submissions:
+
+Patch submissions
+-----------------
+
+Branches must be submitted as merge requests (MR) on GitLab and should have a 
+corresponding issue raised in advance (whenever possible). If it's a small change,
+an MR without it being associated to an issue is okay, but generally we prefer an
+issue to be raised in advance so that we can track the work that is
+currently in progress on the project.
+
+When submitting a merge request, please obtain a review from another committer 
+who is familiar with the area of the code base which the branch effects. Two
+approvals from other committers who are not the patch author will be needed
+before any merge (we use Gitlab's 'approval' feature for this).
+
+Below is a list of good patch submission good practice:
+
+- Each commit should address a specific issue number in the commit message. This
+  is really important for provenance reasons.
+- Merge requests that are not yet ready for review should be prefixed with the
+  ``Draft:`` identifier.
+- Submitted branches should not contain a history of work done.
+- Unit tests should be a separate commit.
+
+Commit messages
+~~~~~~~~~~~~~~~
+
+Commit messages must be formatted with a brief summary line, optionally followed
+by an empty line and then a free form detailed description of the change. The
+summary line must start with what changed, followed by a colon and a very brief
+description of the change. If there is an associated issue, it **must** be
+mentioned somewhere in the commit message.
+
+**Example**::
+
+   worker.py: Fixed to be more human than human
+
+   Gifted the worker with a past so we can create
+   a cushion or a pillow for their emotions and
+   consequently, we can control them better.
+
+   This fixes issue #8.
+
+For more tips, please read `The seven rules of a great Git commit message`_.
+
+.. _The seven rules of a great Git commit message: https://chris.beams.io/posts/git-commit/#seven-rules
+
+.. _coding-style:
+
+Coding style
+------------
+
+Python coding style for BuildGrid is `PEP 8`_. We do have a couple of minor
+exceptions to this standard, we dont want to compromise code readability by
+being overly restrictive on line length for instance.
+
+BuildGrid's test suite includes a PEP8 style compliance check using `flake8`_.
+That test suite is automatically run for every change submitted to the GitLab
+server and the merge request sytem requires the test suite execution to succeed
+before changes can be pulled upstream. This means you have to respect the BuildGrid
+coding style. For convenience you can run `tox -e flake8` to perform these checks.
+
+BuildGrid's CI also runs a static type check in the form of `mypy`_. While mypy
+is stable, it is not yet 1.0 and thus is not able to understand every use case
+in typing (such as recursive types and complex mutators). Nevertheless, type
+annotations are strongly preferred for readability, with complex type issues
+flagged with ``# type: ignore``.
+
+Configuration and exceptions for ``flake8`` can be found in:
+
+- The `setup.cfg`_ file for ``flake8``.
+
+.. _PEP 8: https://www.python.org/dev/peps/pep-0008
+.. _flake8: https://flake8.pycqa.org/en/latest/
+.. _setup.cfg: https://gitlab.com/BuildGrid/buildgrid/blob/master/setup.cfg
+.. _mypy: http://mypy-lang.org/
+
+Automated code formatting should be run using `isort` and `black` before submitting
+MRs to the project. These tools can be invoked by running `tox -e format`.
+
+Imports
+~~~~~~~
+
+Both absolute and relative imports are allowed. Prefer absolute imports when
+possible, but if the absolute import path gets too long, relative imports are
+okay.
+
+Absolute::
+
+  from buildgrid.worker import Worker
+
+Relative::
+
+  from .worker import Worker
+
+
+Symbol naming
+'''''''''''''
+
+Any private symbol must start with a single leading underscore for two reasons:
+
+- So that it does not bleed into documentation and *public API*.
+- So that it is clear to developers which symbols are not used outside of the
+  declaring *scope*.
+
+Remember that with python, the modules (python files) are also symbols within
+their containing *package*, as such; modules which are entirely private to
+BuildGrid are named as such, e.g. ``_roy.py``.
+
+
+Typing
+......
+
+Always add type annotations to your code and ensure that mypy verifies it.
+
+BuildGrid was started before we began adding type annotations to the codebase,
+so you may run across functions that are not annotated. If you do, please leave
+the functions better than you found them and add annotations. mypy was designed
+with `this maintenance pattern <https://mypy.readthedocs.io/en/latest/existing_code.html>`_
+in mind.
+
+.. _codebase-testing:
+
+Testing
+-------
+
+BuildGrid is using `pytest`_ for regression and newly added code testing. The
+test suite contains a serie of unit-tests and also run linting tools in order to
+detect coding-style_ breakage. The full test suite is automatically executed by
+GitLab CI system for every push to the server. Passing all the tests is a
+mandatory requirement for any merge request to the trunk.
+
+.. _pytest: https://docs.pytest.org
+
+
+Running tests
+~~~~~~~~~~~~~
+
+In order to run the entire test suite, simply run:
+
+.. code-block:: sh
+
+   tox -e ci-venv -- pytest tests
+
+pyest's `usage documentation section`_ details the different command line
+options that can be used when invoking the test runner.
+
+.. _usage documentation section: https://docs.pytest.org/en/latest/usage.html
+
+
+Test coverage
+~~~~~~~~~~~~~
+
+We are doing our best at keeping BuildGrid's test coverage score as high as
+possible. Doing so, we ask for any merge request to include necessary test
+additions and/or modifications in order to maintain that coverage level. A
+detailed `coverage report`_ is produced and publish for any change merged to the
+trunk.
+
+.. _coverage report: https://buildgrid.gitlab.io/buildgrid/coverage/
+
+.. _gitlab-features:
+
+GitLab features
+---------------
+
+We intend to make use of some of GitLab's features in order to structure the
+activity of the BuildGrid project. In doing so we are trying to achieve the
+following goals:
+
+- Full transparency of the current work in progress items
+- Provide a view of all current and planned activity which is relatively easy
+  for the viewer to digest
+- Ensure that we keep it simple and easy to contribute to the project
+
+Explanation of how the project is currenlty using some GitLab features:
+
+- `Labels`_: allow us to filter tickets (ie, 'issues' in gitlab terminology)
+  in useful ways. They add complexity and effort as they grow in number, so the
+  general approach is to ensure the ones we have are actually used and are 
+  applied consistently. See the `BuildGrid labels`_. 
+- `Boards`_: allow us to visualise and manage issues and labels in a simple way.
+  Issues start life in the ``Backlog`` column by default, and we move them into
+  ``ToDo`` when we aim to complete them in the current development cycle.
+  ``Doing`` is only for when an item is currently being worked on. When on the
+  Board view, dragging and dropping an issue from column to column automatically
+  adjusts the relevant labels. See the `BuildGrid boards`_.
+  
+  
+Guidelines for using GitLab features when working on this project: 
+  
+- When raising an issue, please:
+   
+  - check to see if there already is an issue to cover this task (if not then 
+    raise a new one)
+  - assign the appropriate label or labels (tip: the vast majority of issues 
+    raised will be either an enhancement or a bug)
+    
+- If you plan to work on an issue, please:
+
+  - self-assign the ticket
+  - ensure the ticket is in the ``ToDo`` column of the board if you aim to 
+    complete in the current sprint but aren't yet working on it, and
+    the ``Doing`` column if you are working on it currently.
+
+- Please note that Gitlab issues are for either 'tasks' or 'bugs' - ie not for 
+  long discussions (where the mailing list is a better choice) or for ranting, 
+  for example.
+  
+The above may seem like a lot to take in, but please don't worry about getting 
+it right the first few times. The worst that can happen is that you'll get a 
+friendly message from a current contributor who explains the process. We welcome
+and value all contributions to the project!  
+
+.. _Labels: https://docs.gitlab.com/ee/user/project/labels.html
+.. _BuildGrid labels: https://gitlab.com/BuildGrid/buildgrid/labels
+.. _Boards: https://docs.gitlab.com/ee/user/project/issue_board.html
+.. _BuildGrid boards: https://gitlab.com/BuildGrid/buildgrid/boards
+.. _Templates: https://docs.gitlab.com/ee/user/project/description_templates.html

buildgrid-0.0.86/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2018 BuildGrid
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

buildgrid-0.0.86/MANIFEST.in

@@ -0,0 +1,24 @@
+# Main package includes:
+include buildgrid/_app/settings/reference.yml
+
+# Data includes:
+include data/config/*.yml
+
+# Documentation includes:
+include docs/source/data/*.yml
+include docs/source/*.rst
+include docs/Makefile
+
+# Tests includes:
+include tests/auth/data/*
+recursive-include tests/cas/data/*
+include tests/cas/data
+
+# Toplevel includes:
+include BuildGrid.doap
+include COMMITTERS.rst
+include CONTRIBUTING.rst
+include LICENSE
+include README.rst
+include requirements.txt
+include pyproject.toml

buildgrid-0.0.86/PKG-INFO

@@ -0,0 +1,85 @@
+Metadata-Version: 2.1
+Name: buildgrid
+Version: 0.0.86
+Summary: A remote execution service
+License: Apache License, Version 2.0
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.8
+License-File: LICENSE
+Requires-Dist: boto3
+Requires-Dist: botocore
+Requires-Dist: dnspython
+Requires-Dist: grpcio-reflection>=1.62.0
+Requires-Dist: grpcio>=1.62.0
+Requires-Dist: janus>=0.6.2
+Requires-Dist: jinja2==3.0.3
+Requires-Dist: protobuf<4.24.0
+Requires-Dist: alembic
+Requires-Dist: Click
+Requires-Dist: SQLAlchemy[mypy]<2.0,>=1.4.24
+Requires-Dist: pydantic>2.0
+Requires-Dist: PyYAML>=6.0.1
+Requires-Dist: jsonschema>=3.0.0
+Requires-Dist: lark-parser
+Requires-Dist: pycurl
+Requires-Dist: buildgrid-metering-client>=0.0.4
+Requires-Dist: mmh3
+Provides-Extra: auth
+Requires-Dist: cryptography; extra == "auth"
+Requires-Dist: PyJWT; extra == "auth"
+Requires-Dist: requests; extra == "auth"
+Provides-Extra: browser
+Requires-Dist: aiofiles; extra == "browser"
+Requires-Dist: aiohttp; extra == "browser"
+Requires-Dist: aiohttp-middlewares; extra == "browser"
+Provides-Extra: database
+Requires-Dist: psycopg2-binary; extra == "database"
+Provides-Extra: redis
+Requires-Dist: fakeredis>=2.10.1; extra == "redis"
+Requires-Dist: redis>=4.5.1; extra == "redis"
+Requires-Dist: hiredis; extra == "redis"
+Provides-Extra: docs
+Requires-Dist: Sphinx<7; extra == "docs"
+Requires-Dist: sphinx-click; extra == "docs"
+Requires-Dist: sphinx-rtd-theme; extra == "docs"
+Requires-Dist: sphinxcontrib-apidoc; extra == "docs"
+Requires-Dist: sphinxcontrib-napoleon; extra == "docs"
+Provides-Extra: tests
+Requires-Dist: coverage; extra == "tests"
+Requires-Dist: cryptography>=38.0.0; extra == "tests"
+Requires-Dist: flaky; extra == "tests"
+Requires-Dist: flask; extra == "tests"
+Requires-Dist: flask-cors; extra == "tests"
+Requires-Dist: moto<4.1.12; extra == "tests"
+Requires-Dist: psutil; extra == "tests"
+Requires-Dist: pycodestyle; extra == "tests"
+Requires-Dist: pyopenssl>=22.0.0; extra == "tests"
+Requires-Dist: pytest; extra == "tests"
+Requires-Dist: pytest-aiohttp; extra == "tests"
+Requires-Dist: pytest-asyncio; extra == "tests"
+Requires-Dist: pytest-cov; extra == "tests"
+Requires-Dist: pytest-forked; extra == "tests"
+Requires-Dist: pytest-pycodestyle; extra == "tests"
+Requires-Dist: pytest-xdist; extra == "tests"
+Requires-Dist: fakeredis>=2.10.1; extra == "tests"
+Requires-Dist: redis>=4.5.1; extra == "tests"
+Requires-Dist: testing.postgresql; extra == "tests"
+Requires-Dist: psycopg2-binary; extra == "tests"
+Provides-Extra: dev
+Requires-Dist: flake8; extra == "dev"
+Requires-Dist: pycodestyle; extra == "dev"
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: pytest-forked; extra == "dev"
+Requires-Dist: pytest-pycodestyle; extra == "dev"
+Requires-Dist: pytest-xdist; extra == "dev"
+Requires-Dist: pip-tools; extra == "dev"
+Requires-Dist: memray; extra == "dev"
+Provides-Extra: mypy
+Requires-Dist: mypy; extra == "mypy"
+Requires-Dist: grpc-stubs>=1.53; extra == "mypy"
+Requires-Dist: boto3-stubs; extra == "mypy"
+Requires-Dist: mypy-boto3-s3; extra == "mypy"
+Requires-Dist: sqlalchemy2-stubs<=0.0.2a22; extra == "mypy"
+Provides-Extra: all
+Requires-Dist: buildgrid[auth,browser,database,dev,docs,mypy,redis,tests]; extra == "all"

buildgrid-0.0.86/README.rst

@@ -0,0 +1,78 @@
+.. image:: https://gitlab.com/BuildGrid/buildgrid/badges/master/pipeline.svg
+    :target: https://gitlab.com/BuildGrid/buildgrid/-/commits/master
+    :alt: pipeline status
+
+.. image:: https://gitlab.com/BuildGrid/buildgrid/badges/master/coverage.svg
+    :target: https://gitlab.com/BuildGrid/buildgrid/-/commits/master
+    :alt: coverage report
+
+.. image:: https://gitlab.com/BuildGrid/buildgrid/-/badges/release.svg
+    :target: https://gitlab.com/BuildGrid/buildgrid/-/releases
+    :alt: coverage report
+
+
+.. _about:
+
+About
+=====
+
+.. _what-is-it:
+
+What is BuildGrid?
+------------------
+
+BuildGrid is a Python remote execution service which implements Google's
+`Remote Execution API`_ and the `Remote Workers API`_. The project's goal is to
+be able to execute build jobs remotely on a grid of computers in order to
+massively speed up build times. Workers on the grid should be able to run with
+different environments. It works with clients such as `Bazel`_,
+`BuildStream`_ and `RECC`_, and is designed to be able to work with any client
+that conforms to the above API protocols.
+
+BuildGrid is designed to work with any worker conforming to the `Remote Workers API`_
+specification. Workers actually execute the jobs on the backend while BuildGrid does
+the scheduling and storage. The `BuildBox`_ ecosystem provides a suite of workers and
+sandboxing tools that work with the Workers API and can be used with BuildGrid.
+
+.. _Remote Execution API: https://github.com/bazelbuild/remote-apis
+.. _Remote Workers API: https://docs.google.com/document/d/1s_AzRRD2mdyktKUj2HWBn99rMg_3tcPvdjx3MPbFidU/edit#heading=h.1u2taqr2h940
+.. _BuildStream: https://wiki.gnome.org/Projects/BuildStream
+.. _Bazel: https://bazel.build
+.. _RECC: https://gitlab.com/BuildGrid/recc
+.. _Trexe: https://gitlab.com/BuildGrid/trexe
+.. _BuildBox: https://buildgrid.gitlab.io/buildbox/buildbox-home/
+
+
+.. _readme-getting-started:
+
+Getting started
+---------------
+
+Please refer to the `documentation`_ for `installation`_ and `usage`_
+instructions, plus guidelines for `contributing`_ to the project.
+
+.. _contributing: https://buildgrid.build/developer/contributing.html
+.. _documentation: https://buildgrid.build/
+.. _installation: https://buildgrid.build/user/installation.html
+.. _usage: https://buildgrid.build/user/using.html
+
+
+.. _about-resources:
+
+Resources
+---------
+
+- `Homepage`_
+- `GitLab repository`_
+- `Bug tracking`_
+- `Mailing list`_
+- `Slack channel`_ [`invite link`_]
+- `FAQ`_
+
+.. _Homepage: https://buildgrid.build/
+.. _GitLab repository: https://gitlab.com/BuildGrid/buildgrid
+.. _Bug tracking: https://gitlab.com/BuildGrid/buildgrid/boards
+.. _Mailing list: https://lists.buildgrid.build/cgi-bin/mailman/listinfo/buildgrid
+.. _Slack channel: https://buildteamworld.slack.com/messages/CC9MKC203
+.. _invite link: https://bit.ly/2SG1amT
+.. _FAQ: https://buildgrid.build/user/faq.html

buildgrid-0.0.86/buildgrid/__init__.py

@@ -0,0 +1,13 @@
+# Copyright (C) 2018 Bloomberg LP
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#  <http://www.apache.org/licenses/LICENSE-2.0>
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.