You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't want to release models without doing run testing first. In order to test a model we need to deploy it in some way first.
This is a chicken and egg or perhaps a cart before the horse problem.
We can solve this by having a pre-release staging area where we automatically deploy models without run testing, and then trigger a pull-request to https://github.com/ACCESS-NRI/access-om2-configs/ with updated model versions (exe paths) to the deployed model in pre-release.
(TBC)
The text was updated successfully, but these errors were encountered:
We don't want to
release
models without doing run testing first. In order to test a model we need to deploy it in some way first.This is a chicken and egg or perhaps a cart before the horse problem.
We can solve this by having a
pre-release
staging area where we automatically deploy models without run testing, and then trigger a pull-request to https://github.com/ACCESS-NRI/access-om2-configs/ with updated model versions (exe paths) to the deployed model inpre-release
.(TBC)
The text was updated successfully, but these errors were encountered: