tree: b02ad7ba28add563ec0f9cb48689dc4b2c022d85 [path history] [tgz]
  1. internal/
  2. proto/
  3. rpc/
  4. .gcloudignore
  5. .golangci.yaml
  6. app.yaml
  7. cron.yaml
  8. main.go
  9. OWNERS
  10. README.md
tree_status/README.md

LUCI Tree Status Service

This service maintains a open/closed status for each “tree” (e.g. chromium). Trees are defined arbitrarily and do not have to correspond 1:1 with a git repo or any other concept.

Each status update optionally includes a text description of why the tree was open/closed.

The tree status is generally used to temporarily stop new CLs from being merged while gardeners fix a broken tree.

Prerequisites

Commands below assume you are running in the infra environment. To enter the infra env (via the infra.git checkout), run:

eval infra/go/env.py

Running tests locally

INTEGRATION_TESTS=1 go test ./...

Running locally

go run main.go \
  -cloud-project luci-tree-status-dev \
  -auth-service-host chrome-infra-auth-dev.appspot.com \
  -spanner-database projects/luci-tree-status-dev/instances/dev/databases/luci-tree-status-dev \
  -frontend-client-id 713057630411-eqah8ap1ptgnf4nnepk10sutqg0msiv1.apps.googleusercontent.com

You can test the RPCs using the rpcexplorer.

Deploy demo instance with local changes to AppEngine

gae.py upload --target-version ${USER} -A luci-tree-status-dev

Deploy to staging

Tree status is automatically deployed to staging by LUCI CD every time a CL is submitted.

Deploy to prod

The prod instance of LUCI Tree Status has not yet been created.