-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add Github HPC actions for ecflow #145
Conversation
The actions have been tested in the integration test of ai-suites: https://github.com/ecmwf/ai-suites/actions/runs/12814765320, in a dedicated PR: https://github.com/ecmwf/ai-suites/pull/16. Everything is working as expected. Do we need to add some tests in the workflows repository? |
Thanks @jjlk, it looks good! @iainrussell, we thought organising the actions using sub-folders would scale better if we add more actions in the future, but feel free to suggest another structure. |
Hi @corentincarton and @jjlk, I like the idea of the subdirectories for this - not quite sure if hpc/ecflow or ecflow/hpc is better. Generally I prefer the latter, but if we might have a bunch of actions that will only ever run on the hpc, then your version is more suitable, so we should probably stick with that (and I think we can say that ecflow tasks will only ever run on hpcs). Can I merge it in now? |
HI @iainrussell , thanks for the comments for me it's ok! |
Here is the result of the last changes on a workflow that uses those actions: https://github.com/ecmwf/ai-suites/actions/runs/12923928972 (everything is green!). |
Merged, and tagged with 'v2' |
This PR aims to add actions related to ecflow server and the HPC.
The idea is to simplify the integration test of the ai-suites repo: https://github.com/ecmwf/ai-suites and to reuse some components in other workflows related to suite execution on HPC in different GIthub repo.
The PR contains three actions to run, monitor (track) and remove the suite.
We (with https://github.com/corentincarton) thought that the actions could be stored in dedicated repositories: