We use ccache with github save/restore to dramatically cut kernel build times (#139).
This works well, but GH has a 10GB limit for all cache entries, and a 7-day TTL for each cache entry.
Which means that if we don't build a kernel for a week,we lose our ccache benefit entirely, which stinks.
The correct way to work around this is to replace GH's cache action with one that saves/restores directly from a dedicated S3 bucket we set up and manage, such as sccache, so we can manage storage and TTLs ourselves.
xref:
We use ccache with github save/restore to dramatically cut kernel build times (#139).
This works well, but GH has a 10GB limit for all cache entries, and a 7-day TTL for each cache entry.
Which means that if we don't build a kernel for a week,we lose our ccache benefit entirely, which stinks.
The correct way to work around this is to replace GH's cache action with one that saves/restores directly from a dedicated S3 bucket we set up and manage, such as
sccache, so we can manage storage and TTLs ourselves.xref:
touchccache entries to keep GH from dropping them after 7 days #161