mastermon: collect step results count

Having the number of steps failing / succeeding in real time helps with
deploying risky changes on steps like update_scripts.

This is the second attempt at this, the first is


Review URL:
2 files changed
tree: fe48abadbcfd317f49eae717025ead8d410a536a
  1. .coveragerc
  2. .gitignore
  4. DEPS
  9. appengine/
  10. appengine_module/
  11. bootstrap/
  12. build/
  13. cipd/
  14. codereview.settings
  15. config/
  16. data/
  17. doc/
  18. docker/
  19. glyco/
  20. go/
  21. infra/
  22. infra_libs/
  24. node/
  27. test/
  29. utils/

infra.git repository

Welcome to the Chrome Infra repository!

Wondering where to start? Check out General Chrome Infrastructure documentation. The rest of this page is specific to this repo.

Entry points

  • wrapper script to run programs contained in subdirectories without having to deal with sys.path modifications.
  • multi-purpose script to run tests.
  • infra_libs/: generally useful functions and classes
  • infra/services/: standalone programs intended to be run as daemons.
  • infra/tools: command-line tools, intended to be run by developers.
  • appengine/: many Chrome-infra-managed AppEngine applications
  • infra/experimental: for, well, experimental stuff. Once they are stabilized and reviewed, they should be moved in a more permanent place.

Miscellaneous technical stuff

  • bootstrap/: utilities to set up a proper Python virtual environment.
  • infra/path_hacks: submodules of this modules give access to modules in the build/ repository. from infra.path_hacks.common import <stg> is actually getting <stg> from build/scripts/common.
  • utils/: purpose? utils?
  • Need to bump infra/deployed to pick up changes?
    • git push origin <updated hash>:deployed
    • mail chrome-troopers@, include:
      • previously deployed hash (for quick rollback)
      • the hash you just pushed
      • the list of CLs that made this push necessary
      • the output of the git push command