Open sfiruch opened 2 years ago
I had a look at it and it seems doable (of course it is). I will also look at commented out tests in this PR and if they can be added to the CSCS testing.
@deiruch I think it would be great if we would have a separate user for testing on CSCS, to clearly see how many hours the testing is using.
Perhaps ask Victor Holanda (CSCS) on how to setup the infra to get automated CI/CD.
Andreas Fink from CSCS suggested we use their dockerized CI infrastructure: https://gitlab.com/cscs-ci/ci-testing/containerised_ci_doc
@kenfus What do you think? Should be easy to use, and webhooks are already supported?
Maybe this would also solve #189, because CSCS requires docker containers anyway...
I think it looks OK and we are currently caching a dev environment as a docker image, so this should be possible. However, I am unsure how exactly docker works with slurm jobs and we would also need access as described in https://gitlab.com/cscs-ci/ci-testing/containerised_ci_doc . I can have a look at it?
I asked CSCS to register our project, so we can test this. I'll post when I hear back from them.
I registered our project with CSCS/Andreas Fink.
CSCS can test docker containers: https://gitlab.com/cscs-ci/ci-testing/containerised_ci_doc and supports webhooks.
There will be a meeting with CSCS on Aug 17 about this exact topic: https://ethz.zoom.us/my/cscsvrdahlia; cscs-dahlia
At least for our releases, we should make sure that they work as expected on CSCS infra. Victor suggested we use ReFrame. We could also use that to confirm that resource-intensive unit tests still work.
It's probably not smart to execute the tests for every commit, because we only get 5000 node-hours. But perhaps running those tests on every PR merge into the main branch might be interesting.