9040e4d720
Building job strings and then parsing them into Work structs seems a bit roundabout when there's no job string to start with. Instead reorient so that we're building a list of Work, and create those Work units directly when possible instead of via job strings. Should be no practical change here. Change-Id: I48f1eec8ab7ccbe2c46fc62174cd3625c51d3732 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/363038 Reviewed-by: Mike Klein <mtklein@google.com> Commit-Queue: Mike Klein <mtklein@google.com> |
||
|---|---|---|
| .. | ||
| bots | ||
| canvaskit | ||
| cmake | ||
| config | ||
| cross-compile/docker/cross-linux-arm64 | ||
| docker | ||
| gcc | ||
| lottiecap | ||
| pathkit | ||
| project-config | ||
| skqp | ||
| wasm-common | ||
| README.md | ||
This directory contains infra-specific files. The branch-config/ directory contains configs that are specific to the master branch (e.g. config for the CQ committing to the master 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).