Use matrices for tier2 tests, compare against last stable version and publish results#30
Use matrices for tier2 tests, compare against last stable version and publish results#30
Conversation
Refactor workflow to use environment variable for CI base path and streamline job dependencies.
|
Also, the changes in GEOS-ESM/swell#677 are imminent, suite names for marine ones should be changed. We should do another PR for tier1 names (e.g., 3dvar -> 3dvar_marine). |
|
Oops, I clicked on send too soon. Would this approach keep the |
|
This wouldn't change how the stable version works, which is that it gets removed if the current build is stable. I may revert the change that uses the stable build, it seems like we want to have more manual control over it. I also can't figure out why it's choosing to skip over the comparison tests completely when they are requirements for the final steps |
|
I know Tier2 has been down for a while. I created a new build under:
This is when |
This PR updates the tier2 tests to use the matrix structure introduced in #29. It also enables comparison testing against the latest stable run of tier2 tests. We can update swell to use the build of JEDI from the latest stable tier2 tests, which will allow the build to be automatically updated if it passes with zero diff. The
publish_comparisonstask introduced in GEOS-ESM/swell#702 will post the results to dataportal if it isn't zero diff.This is a draft for now, I haven't tested this as I want to get #29 in before overwriting the test branch