Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider Input Requirements #191

Open
CodeGat opened this issue Feb 14, 2025 · 0 comments
Open

Consider Input Requirements #191

CodeGat opened this issue Feb 14, 2025 · 0 comments
Assignees
@CodeGat
Labels
CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:investigation look into options, do some research!

Comments

@CodeGat
Copy link
Member

CodeGat commented Feb 14, 2025

Similar to how build-cd makes use of a spack.yaml file, as well as the config/versions.json as indirect input to their entrypoint workflows, consider the same requirements for build-ci. This will require close collaboration with Model Component Repository maintainer expectations.

Considerations

  • Accommodate multiple spack.yaml locations, and even multiple files within one MCR.
  • Determine how we pick out versions of spack-packages/spack-config. Currently we use a static file in build-cd, but maybe it would be worth making it a input to the entrypoint workflow, in the case one wants a GitHub-Actions-level parallelism.
@CodeGat CodeGat added CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:investigation look into options, do some research! labels Feb 14, 2025
@CodeGat CodeGat self-assigned this Feb 14, 2025
@github-project-automation github-project-automation bot moved this to New Issues 🌅 in Build-ci 2.0 Feb 14, 2025
@CodeGat CodeGat moved this from New Issues 🌅 to Todo ⏳ in Build-ci 2.0 Feb 16, 2025
@CodeGat CodeGat mentioned this issue Feb 19, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CodeGat CodeGat

Labels
CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:investigation look into options, do some research!
Projects
Build-ci 2.0
Status: Todo ⏳
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CodeGat