Skip to content

fix(ci): preserve existing Kache config - #19

Open
jmagar wants to merge 5 commits into
mainfrom
fix/preserve-existing-kache-config-20260802
Open

fix(ci): preserve existing Kache config#19
jmagar wants to merge 5 commits into
mainfrom
fix/preserve-existing-kache-config-20260802

Conversation

@jmagar

@jmagar jmagar commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • preserve any existing non-empty Kache config on persistent/self-hosted runners
  • continue generating filesystem or local-only config on clean runner homes
  • prevent CI jobs from stripping dookie's NFS remote and daemon settings

Incident

A temporary self-hosted runner on dookie rewrote ~/.config/kache/config.toml to a 40 GiB local-only file because /home/runner/kache-remote was absent. This guard keeps host-owned configuration intact.

Validation

  • existing config path: preserved
  • empty runner home with writable farm remote: generated filesystem config
  • empty runner home without remote: generated local-only fallback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant