5fb37db69f
One very important, but agonizing to discover, change was to go_repositories.bzl. Without it, we see cryptic errors like: external/org_chromium_go_luci/cipd/api/cipd/v1/BUILD.bazel:22:17: no such package '@org_chromium_go_luci//go.chromium.org/luci/cipd/api/cipd/v1': BUILD file not found in directory 'go.chromium.org/luci/cipd/api/cipd/v1' of external repository @org_chromium_go_luci. Add a BUILD file to a directory to mark it as a package. and referenced by '@org_chromium_go_luci//cipd/api/cipd/v1:api_go_proto' The rest of these changes are very similar to https://skia-review.googlesource.com/c/buildbot/+/514074 which also has justification for the use of task drivers, even in a Bazel-driven world. All the BUILD.bazel files under infra/bots/task_drivers were generated by Gazelle. Note that the infra/bots/BUILD.bazel can happily build and package up the task drivers from the infra repo. The old build_task_drivers tasks did this too, because we have some task drivers that are used in both repos. Change-Id: I13c46c62bc7a6a4bfe7935b28efbfb34caabb6f2 Bug: skia:12541 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/515296 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com> |
||
|---|---|---|
| .. | ||
| bots | ||
| canvaskit | ||
| cmake | ||
| config | ||
| cross-compile/docker/cross-linux-arm64 | ||
| docker | ||
| gcc | ||
| lottiecap | ||
| pathkit | ||
| project-config | ||
| wasm-common | ||
| README.md | ||
| skcq.json | ||
This directory contains infra-specific files. The branch-config/ directory contains configs that are specific to the main branch (e.g. config for the CQ committing to the main branch), while project-config/ directory contains project-wide configuration (e.g. list of buckets for cr-buildbucket service and list of refs known to the infra services).