For discussion only: batch install to support automated builds on Ursa #1788
Conversation
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
…1/ursa/packages_oneapi.yaml for building unified environment on Ursa for spack-stack develop as of 2025/10/02
…ll.sh to support batch installs on Ursa
climbfuji
requested review from
rickgrubin-noaa,
RatkoVasic-NOAA and
ulmononian
Merged
10 tasks
rickgrubin-noaa
approved these changes
Oct 2, 2025
ulmononian
reviewed
Oct 3, 2025
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.
Description
This PR is not to be merged as is. It is mean to be used for discussion on how to best automate spack-stack builds for regular (nightly, etc) builds and deployments. If we decide to pursue this path, then the batch install script should be generalized, cleaned up, and potentially split to better support the needs of the partner organizations.
Also, there is a related effort by @AlexanderRichert-NOAA who is working on a
spack deploycommand.The path forward is yet to be determined.
Timing
After an initial build and population of the various caches, subsequent full rebuilds and deployments from the cache take about 45 minutes each for the unified environment with two compilers.
Dependencies
None, but this PR includes the changes from PR #1787, which will be merged into develop.
Issues addressed
Working towards automated spack-stack installs on Ursa. Part of project spack-stack automation.
Applications affected
None
Systems affected
Ursa
Testing
n/a
Checklist
n/a