Add scheduled tests to auto-qual response

BUG=None
TEST=Tested recipe.
TEST=$HOME/chromiumos/infra/proto_branched/generate.sh &&
$HOME/chromiumos/chromite/api/compile_build_api_proto && ./recipes.py -O
chromiumos_proto=$HOME/chromiumos/infra/proto_branched test train

Change-Id: I705b89ad2d7b249af7c62bc664f1ee755257c400
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/7899946
Reviewed-by: Jon Murphy <jpmurphy@google.com>
Commit-Queue: Jon Murphy <jpmurphy@google.com>
Auto-Submit: Jeremy Bettis <jbettis@chromium.org>
3 files changed
tree: 3f1425dc841fc0ae294568c9e571e1ffd21da64d
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  11. generate.sh
  12. LICENSE
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  16. PRESUBMIT.py
  17. README.md
  18. setup_cipd.sh
  19. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.

When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.