Skip to content

Tune CI: cancel stale runs, cache SDK/registry, split fmt - #48

Merged
Linuxuser67 merged 1 commit into
mainfrom
ci-tuneup
Sep 18, 2026
Merged

Linuxuser67 merged 1 commit into
mainfrom
ci-tuneup

Conversation

@Linuxuser67

Copy link
Copy Markdown
Owner

Measured on the alpha.13 release build (~7.5 min: setup/apt ~2, SDK ~1, flatpak build ~5.5, bundle ~0.5):

  • concurrency cancel-in-progress on PR runs only (ci + flatpak-test): rapid pushes no longer queue full duplicate builds. Main pushes, manual dispatches and release builds never cancel.
  • Cache the GNOME SDK/Platform layer (~/.local/share/flatpak + ~/.cache/flatpak, keyed by manifest incl. runtime-version) in the shared flatpak build chain and the tarball job; tarball also caches the cargo registry (keyed by Cargo.lock). Builds stay force-clean/pristine — only downloads are cached. Release provenance unchanged.
  • Split cargo fmt into its own dependency-free ubuntu job (~1 min signal) instead of riding the Fedora container job.

Deliberately untouched: the 5.5 min dep recompile (would fight the force-clean doctrine), retention, timeouts, path filters, release triggers.

@Linuxuser67
Linuxuser67 merged commit 5a03c17 into main Sep 18, 2026
3 checks passed
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