-
Notifications
You must be signed in to change notification settings - Fork 45
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.
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
Reusable workflow #201
Reusable workflow #201
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jedwards4b This looks great. BTW, why we are not going with spack for the dependencies. I know you were working with it. You could get rid of all those actions.yaml files for each individual dependency. Maybe you are looking for more control over those dependency. Not sure.
@jedwards4b BTW, thanks for fixing ieee issue. I was not aware of that CPP flag. I am still using my own CDEPS for because of it but maybe I could switch to master after this PR in. |
I have considered using spack and/or using containers and we may go there later, but for now I am happy to |
Description of changes
Create reusable workflows and stop duplicating code
Specific notes
Contributors other than yourself, if any:
CDEPS Issues Fixed (include github issue #):
Are there dependencies on other component PRs (if so list):
Are changes expected to change answers (bfb, different to roundoff, more substantial):
Any User Interface Changes (namelist or namelist defaults changes):
Testing performed (e.g. aux_cdeps, CESM prealpha, etc):
Hashes used for testing: