Unleash / unleash / 31475870144

87%

master: 91%

push

github

chore: backend sharding

Small backend CI sharding comparison and would like your take on the
trade-off.
-
[Unsharded](https://github.com/bricks-software/unleash-enterprise/actions/runs/30802484505):
8m31s wall-clock / runner time.
- [4 backend
shards](https://github.com/bricks-software/unleash-enterprise/actions/runs/30832960347):
slowest shard finished in 4m06s, so the backend result arrived ~4m25s
earlier.
- The problem is the four shard jobs consumed 14m41s total runner time.
Almost 2× the unsharded run, due to duplicated PostgreSQL startup,
checkout, install, lint, and build.

The trade-off: roughly halve feedback time when capacity is available,
in exchange for 2x compute time.

There is also a minor benefit when rerunning failed tests (potentially
flaky): you can rerun one shared instead of a full ~8 minute full job.

1985 of 2187 branches covered (90.76%)

15737 of 17994 relevant lines covered (87.46%)

836.93 hits per line