doc: document the filesystem-image step; ci: serialize gh-pages deploys#262
Merged
Conversation
A burst of pushes (e.g. several PRs merged to main within seconds) could race multiple gh-pages deployments, failing with "in progress deployment". Add a concurrency group keyed on the ref with cancel-in-progress so only the latest run deploys.
build.sh bsp-so3 only compiles; the empty SD-card image is produced by the privileged 'filesystem' recipe (losetup/mkfs/parted), and deploy.sh populates but does not create it. Document the canonical first-build sequence (build.sh bsp-so3 -> build.sh -x filesystem -> deploy.sh bsp-so3) in the build system + user guide (incl. the AVZ-guest path), and point run.sh's missing-image error at the filesystem step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-ups to the ci-deploy work (#261).
docs —
build.sh bsp-so3only compiles; the empty SD-card image is created by the separate, privilegedfilesystemrecipe (losetup/mkfs/parted), anddeploy.shpopulates but does not create it. A deploy against a fresh tree fails until the image exists. Documents the canonical first-build sequence in the build-system reference and the user guide (including the AVZ-guest path):and points
docker/scripts/run.sh's missing-image error at thefilesystemstep.ci — add a
concurrencygroup (keyed on the ref, cancel-in-progress) to the Docs workflow so a burst of pushes doesn't race multiple gh-pages deployments ("in progress deployment" failures).