CI for config repos?

[aekiss]

There are 12 supported configurations in the master and master+bgc branches of these repositories, which have no CI at the level of the repos
https://github.com/COSIMA/1deg_jra55_iaf
https://github.com/COSIMA/025deg_jra55_iaf
https://github.com/COSIMA/01deg_jra55_iaf
https://github.com/COSIMA/1deg_jra55_ryf
https://github.com/COSIMA/025deg_jra55_ryf
https://github.com/COSIMA/01deg_jra55_ryf

It could be helpful to have CI triggered by pushes or PRs to the master and master+bgc branches of these repos. At present there is no CI on the master+bgc branches, and the master branches only get CI when there's a PR that updates the submodules in https://github.com/COSIMA/access-om2/tree/master/control.

Would that be easy to set up? I'm thinking a short run and maybe a reproducibility check. I guess a lot of the CI stuff in https://github.com/COSIMA/access-om2 could be reused. Not sure if that's practical for the 0.1deg configs though?

[aidanheerdegen]

When you say CI do you mean actual model runs, or checks on the config.yaml like

https://github.com/COSIMA/01deg_jra55_iaf/blob/master/.travis.yml

[aekiss]

I was thinking a short run, but really anything would be better than nothing. Not a high priority though - they don't get updated that often and I usually do a test run for anything sketchy.