CI: Add datafile for consistency with other MCRs#728
Merged
Conversation
Contributor
|
Can the entries in |
Contributor
Author
|
Either by naming them differently in the same datafile, or via different datafiles themselves, sure! |
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
2 participants
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.
Background
Currently,
CABLEis the only Model Component Repository that doesn't usebuild-cisinputs.spack-manifest-data-pathinput. It's not required by MCRs, but for an update to the CI inaccess-spack-packages(see ACCESS-NRI/access-spack-packages#420) which tests manifests defined in model component repositories, it would be much simpler if this repository had one.If there are changes to the manifests in the future, more common data can be added to this file, as well!
The PR
.github/build-ci/data/standard.json, a file that defines key-value pairs that are usable in.github/build-ci/manifests/*.spack.yaml.j2files. Currently, only onetarget: x86_64is defined.x86_64with{{ target }}in the manifest, which will be replaced at spack install timeinputs.spack-manifest-data-pathto thebuild-ciworkflow call📚 Documentation preview 📚: https://cable--728.org.readthedocs.build/en/728/