| name | build | ||||||
|---|---|---|---|---|---|---|---|
| description | Build, validate, and test image changes. Use for Containerfile, build scripts, image contents, or local validation. | ||||||
| metadata |
|
- Editing
Containerfile,build_files/,system_files/, or image inputs. - Running local validation or deciding whether a full build is necessary.
- Debugging a workflow: use ci.
- Changing package placement: use packages.
- Reviewing trust boundaries: use security.
- Read the affected source and
../../architecture.md. - Run the lightest checks first:
just check
pre-commit run --all-files- For shell or hook changes, run:
bats tests/unit/- Build only when image assembly changed:
just build <image> <stream> <flavor>
just clean- Do not update the unused
build_files/shared/build.sh. - Keep
build_files/base/04-install-kernel-akmods.shas an entrypoint wrapper; the orchestration logic lives in04-install-kernel-akmods.py. /tmpdoes not persist between containerRUNinstructions.- Preserve Containerfile cache boundaries.
- Report expensive builds accurately.
A build task is complete only when the relevant focused checks pass and any required image validation is reported honestly.
Use for Build or image changes.
Do not use for Pure workflow, package-placement, or security-policy work.
Read the source, run focused checks, then run the default gate.
- "A shortcut is harmless." Follow the source-of-truth and verification rules instead.
- Full builds for documentation-only changes; editing dead orchestration code.
- The selected source and focused command were checked.
- The repository default gate passes.