prashantdivate Yocto CI Release
Workflow
- Identify source orchestration:
kas,repo, submodules, manifest repo, or monorepo. - Pin every layer and external source needed for reproducibility.
- Separate caches from build output:
DL_DIR,SSTATE_DIR, hash equivalence, container caches, and artifacts. - Build the smallest useful CI matrix: parse, recipe smoke, image, SDK, QEMU/testimage, hardware smoke where available.
- Publish signed and checksummed artifacts with machine, distro, image, git refs, build config, license data, and SBOM if enabled.
- Keep secrets out of
local.conf, logs, and artifacts.
References
- ci-release-playbook.md: CI pipeline patterns, cache strategy, release artifact checklist.
Guardrails
- Do not use floating branch refs for release builds.
- Do not persist
tmp/as a cache unless the project explicitly accepts the fragility. - Do not publish images without checksums and provenance.
- Do not run hardware flashing in CI without explicit device targeting and recovery controls.