ci: use a Turborepo remote cache for the monorepo build #39
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
qa:preview
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
quatrain/core!39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/38-turbo-remote-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?
Closes #38
Change
turbo.json:remoteCache.signatureenabled..forgejo/workflows/ci.yaml: the build step setsTURBO_CACHEso that pushes todevelopandmainread and write the remote cache, and every other ref only reads. The publish step setsTURBO_CACHE: local:rw.guidelines/CONTRIBUTING_AGENTS.mddescribes the build cache.The address and the credentials of the cache are not in this repository nor in its forge settings: the runners give them to every job (
qtrn-io/clusterpull request 58). Nothing has to be configured on the organisation.Safe to merge before the cache exists
Without the settings Turborepo prints that remote caching is disabled and builds everything, as today.
Verified locally
Against the cache server in a container:
PUTreaches the server).signature: true.Against a listener that records requests, with the cache credentials present in the environment:
TURBO_CACHE: local:rwTurborepo printsRemote caching disabled (by flags)and neither reads nor writes an artifact. It still sends one usage event (POST /v8/artifacts/events).Not verified: the cache on the forge itself, which needs the server and the runner change of
qtrn-io/clusterpull request 58.🤖 Generated with Claude Code