ci: make "create cache" a reusable workflow#91
Merged
jjuyeonkim merged 3 commits intoOct 27, 2025
Conversation
7 tasks
fmalatino
approved these changes
Oct 24, 2025
twicki
approved these changes
Oct 24, 2025
Collaborator
twicki
left a comment
There was a problem hiding this comment.
Nice. I don't fully get the magic, but if it works it works!
Collaborator
|
My experience with workflows is limited, so I don't have feedback other than it looks useful. |
jjuyeonkim
approved these changes
Oct 24, 2025
8 tasks
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.
Description
Recent (planned) downtime of NCCS portal showed a whole in our translate test data caching strategy. When we run pyFV3 tests as re-usable workflow in e.g. NDSL tests, we don't cache the translate test data. To do so, we can "upgrade" the "create cache" workflow to be re-usable such that we can call it from e.g. NDSL when we create the cache there.
GHA doesn't provide a way to detect
workflow_callas an event (e.g.github.eventwill beworkflow_dispatchin that case, which is the same as for a manual dispatch). We thus create an artificial input in case the workflow is called from another workflow. That way we know. The artificial input has a default value such that we don't need to set it from the calling workflow.How Has This Been Tested?
Tested on my fork, e.g. romanc/NDSL#5.
Checklist:
Depends on ci: make "create cache" a reusable workflow pySHiELD#69