bazelbuild / bazelbuild/continuous-integration
Collect CI performance metrics on per-target level
Open
FR
P1
- Dominant language
- Python
- Stars
- 302
- Forks
- 194
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 41
Description
Thanks to sharding it's really hard to find the performance of a single test, especially across multiple builds. Moreover, thanks to bazel-diff the target might not have been run at all.
We're already analyzing test_bep.json when --print_shard_summary is set. Consequently, it should be easy to dump per-target metrics into some database (Cloud SQL or whatever).
Contributor guide
Assessment
This issue has not been assessed yet.