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
http://crrev.com/1507093003

BUG=601607

Review URL: https://codereview.chromium.org/1877953002
2 files changed
tree: fe48abadbcfd317f49eae717025ead8d410a536a
  1. appengine/
  2. appengine_module/
  3. bootstrap/
  4. build/
  5. cipd/
  6. config/
  7. data/
  8. doc/
  9. docker/
  10. glyco/
  11. go/
  12. infra/
  13. infra_libs/
  14. node/
  15. test/
  16. utils/
  17. .coveragerc
  18. .gitignore
  19. codereview.settings
  20. CONTRIBUTING.md
  21. DEPS
  22. LICENSE
  23. navbar.md
  24. OWNERS
  25. PRESUBMIT.py
  26. README.md
  27. run.py
  28. test.py
  29. testjs.py
README.md

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

  • run.py: wrapper script to run programs contained in subdirectories without having to deal with sys.path modifications.
  • test.py: 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