Skip to content

Add CI cache reset control #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ATAC-Helicopter merged 1 commit into from
Jul 29, 2026
Merged

Add CI cache reset control #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/build-container.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@ on:
required: true
type: string
default: foundation
reset_cache:
description: Ignore cached layers and replace the cache after corruption or stale build inputs
required: true
type: boolean
default: false

permissions:
contents: read
Expand Down Expand Up @@ -68,6 +73,7 @@ jobs:
platforms: linux/amd64
push: ${{ inputs.publish }}
pull: true
no-cache: ${{ inputs.reset_cache }}
tags: ${{ env.IMAGE_REF }}
cache-from: type=gha,scope=developer-os-amd64
cache-to: type=gha,mode=max,scope=developer-os-amd64
Expand Down
4 changes: 4 additions & 0 deletions prototype/docs/CI.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,10 @@ reusable cache. Bootc images are deliberately not loaded into Docker's classic
local image store because their deep layer history can exceed Docker's import
limit.

Leave **Reset cache** disabled for normal builds. Enable it if BuildKit reports
a truncated cached layer, `short read`, or `unexpected EOF`; the run will ignore
the damaged entry and replace it with a fresh cache.

### Build bootable disk

Run `build-disk.yml` after the container workflow succeeds. It starts a
Expand Down