Repository navigation
Document where the containers are published and how to rebuild them - #190
Merged
Merged
Conversation
Raul asked where the newest image is and how to rebuild it. Both answers lived only in the build workspace on BIC and in my own notes, so write them down next to the scripts: the published paths and how to verify them, the workspace layout build_beta_server.sh expects, where every item in downloads/ comes from, the incremental-rebuild path that reuses the BIC workspace, the traps (the version stamp, the refusal to overwrite an artifact, the unguarded code tree), the in-image smoke test, and the publish 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
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.
Raúl asked where the newest container is and how to rebuild it. Both answers
lived only in the build workspace on BIC and in my own notes, so this writes
them down next to the scripts that do the work.
containers/README.mdcovers:/data_/mica1/01_programs/singularity/, which variant to take, the filesbeside them, how to verify a checksum, and how to read an image's own
BUILDINFO.json/CONTAINER_VERSION.layout
build_beta_server.shexpects, and the incremental path that reusesthe existing BIC workspace — about 15 minutes per variant when only
micapipe's own code changed.
downloads/from scratch, item by item, with the upstreamsource for each and which ones
SOURCES.sha256gates. There is no fetchscript, and that was nowhere written down.
versions.json,package_beta.shrefuses to overwrite an artifact, and the code tree iscopied in unguarded so
runtime/opt/micapipehas to be removed or you shipthe old code.
enough on its own — both beta.3 defects passed every static check.
Also adds a pointer to it from
docs/validation/v1-beta-3.md.Docs only; no pipeline code touched.