Google Git
Sign in
chromium / infra / luci / luci-py / 2496d1f878928716790cdd252335b4b086a89c0e
commit2496d1f878928716790cdd252335b4b086a89c0e[log] [tgz]
authorVadim Shtayura <vadimsh@chromium.org>Fri Feb 14 02:46:26 2020
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Feb 14 02:46:26 2020
tree397a08f4d53df278f5d412679dfe3c62fde1f2fa
parentaaae545ae91286e4b2515a23ff33d30fea6a6564 [diff]
[realms] Add initial protos with initial documentation.

There are two category of proto messages:
  * Messages used to describe user-facing realms.cfg file.
  * Messages used to describe the internal representation of realms.

They have different "target audiences" and different scopes of who
should rely on them. "Public" messages will be written by end users
and by lucicfg, and parsed only by auth_service. Internal messages
will be generated by auth_service and parsed by ALL other LUCI
services (but never by end users).

Thus we put "public" messages in auth_service/proto/realms_config.proto
and "internal" ones in components/auth/proto/realms.proto.

R=iannucci@chromium.org, tandrii@chromium.org
BUG=1051724

Change-Id: I5239f48f4982e338c09021a85d7b258833f48133
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-py/+/2053043
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
6 files changed
tree: 397a08f4d53df278f5d412679dfe3c62fde1f2fa
  1. appengine/
  2. client/
  3. .gitattributes
  4. .gitignore
  5. .style.yapf
  6. .vpython
  7. .vpython3
  8. .yapfignore
  9. AUTHORS
  10. codereview.settings
  11. CODING_STYLE.md
  12. CONTRIBUTORS
  13. DEPS
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
README.md

LUCI

LUCI is an ensemble of services that work together to run large scale CI (continuous integration) infrastructure to get results in O(1). It is used by the Chromium project.

See appengine/ for the services provided.

Overview

A complete CI toolkit:

  • Strict separation between task distribution and file distribution.
    • Swarming distributes tasks across an army (thousands) of Swarming bots.
    • Isolate server distributes 10s of thousands of files per task.
  • Federated authentication and ACL.
  • git based configuration data propagation.
  • Automatic Google Compute Engine VM recycling.
  • Windows, OSX and Linux (Ubuntu), used with Android, iOS, ChromeOS.
  • Written in python 2.7 along Go tools.
  • Used by the Chromium infrastructure and other teams.

Installing

  1. Install Google AppEngine SDK.
  2. git clone https://chromium.googlesource.com/infra/luci/luci-py

Code layout

Versioning

  • Branch master constains the latest code.
  • Branch stable contains the stable code.

Contributing

  • Sign the Google CLA.
  • See the coding style.
  • Make sure your user.email and user.name are configured in git config.

Run the following to setup the code review tool and create your first review:

git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools
export PATH="$PATH:$HOME/src/depot_tools"
cd luci-py
git checkout -b work origin/master

# hack hack

git commit -a -m "This is awesome\nR=joe@example.com"
# This will ask for your Google Account credentials.
git cl upload -s
# Wait for LGTM over email.
# Check the commit queue box in codereview website.
# Wait for the change to be tested and landed automatically.

Use git cl help and git cl help <cmd> for more details.

Style

The preferred style is PEP8 with two-space indent; that is, the Chromium Python style, except functions use lowercase_with_underscores. Use yapf (git cl format) to autoformat new code.

License

This project is licensed under Apache v2.0 license. See LICENSE for details.