Google Git
Sign in
chromium / infra / infra.git / 9e2cc21b8fddf8ccd9ca4c80095de3b205de343c
commit9e2cc21b8fddf8ccd9ca4c80095de3b205de343c[log] [tgz]
authorNodir Turakulov <nodir@google.com>Fri Jun 14 23:51:16 2019
committerCommit Bot <commit-bot@chromium.org>Fri Jun 14 23:51:16 2019
tree817c6599e91b578ae2682a93f4d1ecc511890f15
parent86e0545371f652f5809e308e37c3bd10b6578b4a [diff]
[buildbucket] Apply global settings

https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1656174
added a few global settings. Apply logdog host and global caches.
Do not apply known gerrit hosts: those will be propagated via args
of the LUCI runner. It is not present in Build proto.

R=tandrii@chromium.org

Bug: 939368
Change-Id: I6fd497fa6aced9fa87df79464ca433a379d01188
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/1656310
Commit-Queue: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#23704}
7 files changed
tree: 817c6599e91b578ae2682a93f4d1ecc511890f15
  1. 3pp/
  2. appengine/
  3. appengine_module/
  4. bootstrap/
  5. build/
  6. cipd/
  7. crdx/
  8. data/
  9. doc/
  10. docker/
  11. glyco/
  12. go/
  13. infra/
  14. node/
  15. packages/
  16. recipes/
  17. test/
  18. utils/
  19. .gitattributes
  20. .gitignore
  21. codereview.settings
  22. CONTRIBUTING.md
  23. DEPS
  24. LICENSE
  25. navbar.md
  26. OWNERS
  27. PRESUBMIT.py
  28. README.md
  29. run.py
  30. test.py
  31. WATCHLISTS
  32. WHITESPACE
README.md

infra.git repository

Welcome to the Chrome Infra repository!

Wondering where to start? Check out General Chrome Infrastructure documentation. In particular, to check out this repo and the rest of the infrastructure code, follow the instructions here. 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.
  • packages/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

Integrating tests with test.py

If you've added a new module, integrate your tests with test.py:

  1. Create a .coveragerc file in the root directory of the module you want to test. Take a look at another .coveragerc to see what to include in that.
  2. Create a “test” directory in the root directory of the module you want to test. More your *_test.py files to this directory.

Double-check that your tests are getting picked up when you want them to be: ./test.py test <path-to-package>.

Tests still not getting picked up by test.py? Double-check to make sure you have init.py files in each directory of your module so Python recognizes it as a package.