Cache sbt 2 build output in the coverage job

[stasimus]

The coverage job rebuilt everything every run. cleanFull wiped sbt's action cache, and the cache alone isn't enough: it restores classes but not scoverage's scoverage-data, so a hit crashed the tests. ~/.cache/sbt and target/out now share one entry, stale measurements get dropped, cleanFull is off.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 333360d0-f061-4ed5-97ab-61e2f8a003bb

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[stasimus]

Why this is worth doing: test-coverage was the one job guaranteed to do a cold, full, instrumented build on every run. disk-cache: false meant nothing was restored, and cleanFull cleared sbt's action cache anyway, so even a restored cache would have been thrown away before the first compile.

	sbt elapsed	recompiled
cold, no cache	13 s	45 + 33 + 6 sources
rerun, nothing changed	2 s	none
one source file changed	5 s	1 source

[mr-git]

I read the description and comment, but I do not understand what this fixes

[stasimus]

Not a bugfix. The intention is to include the coverage phase into the cache, so builds get faster.