Keep CI's Go module cache deletable, and use the runner's sqlc #23
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/ci-module-cache"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
serverjob for27c87b4failed ondev, after the same commit had passed on its branch, so staging stayed onffc1615. These two changes are the fix.Module cache
Go makes its module cache read-only, so the runner could not delete a
serverjob's workspace afterwards. Each run left its modules, about 800M with sqlc's, on the runner's tmpfs until it filled.GOFLAGSnow includes-modcacherw, which keeps the cache writable and the workspace removable.sqlc from the runner
sqlc now comes from the runner's image instead of being built from
tools/go.modon every run; building it accounted for most of those modules. Beforesqlc diff, the job checks that the runner'ssqlc versionmatches the releasetools/go.modpins (currentlyv1.31.1on both sides). README notes that the runner needs sqlc and that the two are bumped together.Local development is unchanged:
go tool -modfile=tools/go.mod sqlc generatestill works.After merging
Staging should move from
ffc1615to this commit, which also brings the OpenBao/Vault fix from #22.