tree: a1538b6991a302cb49df8878d9c84d2e9c2d28e7 [path history] [tgz]
  1. api/
  2. buildsource/
  3. common/
  4. frontend/
  5. git/
  6. rpc/
  7. ui/
  8. .gcloudignore
  9. .gitignore
  10. app.yaml
  11. cron.yaml
  12. index.yaml
  13. main.go
  14. Makefile
  15. OWNERS
  17. service-pubsub.yaml

Milo - The UI for LUCI.

Milo is the user interface for LUCI. It displays information from Buildbucket and ResultDB about builders, builds, and test results, and can be configured to display custom consoles.


Releases are automatically pushed to luci-milo-dev on commit by the gae-deploy builder.

To push to prod, the steps are:

  1. Get an infra_internal checkout
  2. cd data/gae
  3. vim apps/luci-milo/channels.json
  4. Modify the “stable” version in channels.json (e.g. by reusing the current staging version).
  5. Run ./ to regenerate the Makefile.
  6. Create a CL and add release notes to the description, as follows:
    1. Get the commit hashes from the old and new versions. E.g. in channels.json, if you changed the stable version from “31039-7badeba” to “31164-781e143”, the old commit hash is 7badeba and the new commit hash is 781e143. These correspond to commits in the infra/infra repo.
    2. Navigate to the DEPS file in the corresponding commits on Gitiles, e.g. (old) and (new).
    3. Check the pinned commit of [infra/luci/luci-go] in the DEPS file at these commits. For example, the commits in this case are: 2bdb75fedc327ab79d4f514c394a90033f6be375 (old) and a4f26ffd812e4299eacf6d6ae26f01252a88164d (new).
    4. Run git log between these two commits:
      git log 2bdb75fedc32..a4f26ffd812e --date=short --first-parent --format='%ad %ae %s'
    5. Add the resulting command line and output to the CL description. Example:
  7. Mail and land the CL.
  8. Send an email to luci-releases@ to let people know you've done a new release, and link to the push CL.