Test coverage is what I’d need the most. It would let me see at a glance which projects don’t have enough tests, and public shame the owning team
Now, we could imagine many other metrics worth monitoring: the time to perform a specific step in the pipeline, the size of the artifacts, …
Here is a proposal on how this could work:
I believe we could leverage the meta-data functionality to define builds custom metrics. Something like that:
- label: Run tests
- label: Code coverage
<perform tests + collect coverage metric>
buildkite-agent meta-data set "code_coverage" "$COVERAGE"