Update ci config

[anton-seaice]

Closes #193 and #162

@jo-basevi : if you can check syntactical correctness that would be great. also, can we use payu main branch or does it have to be a tagged version ?

@dougiesquire : we could make a special condition to run restart repro on specific test branches if desired ? (e.g. for all branches which contain the word repro ?)

[jo-basevi]

can we use payu main branch or does it have to be a tagged version ?

The payu module is used as a base when building the test python virtual environments on gadi (smaller environment size compared to building them from scratch). So there's an option for "payu-version": "dev" which will load the payu/dev module.

[anton-seaice]

Ok - this might be correct now. My idea is:

run all dev branches using payu/dev module and main branch from model-config-tests

run all release branches using released version

run repro tests more often (which also checks for changes in dependencies too)

[jo-basevi]

Thanks, just have a couple questions/comments. With the top-level defaults being payu/dev module and main branch from model-config-tests, I think "repro" and "scheduled" could have a release-.* section to set fixed versions

        "release-.*": {
            "model-config-tests-version": "0.0.12",
            "payu-version": "1.1.6"
        },

Is "release-1deg_jra55do_ryf" about to be an existing branch? Adding it in the "scheduled" section will trigger a scheduled test for it which it should fail if it can't find the branch.

[anton-seaice]

All good thinking @jo-basevi

I think "repro" and "scheduled" could have a release-.* section to set fixed versions

I might have it right now :-)

[jo-basevi]

Thanks @anton-seaice, the changes look good to me