When switching CI recently, I stopped it from spamming quay.io with a Cactus image for every single commit. This means that --binariesMode docker will no longer work by default, since it will look for a commit-tagged image that isn't there.
This PR switches --binariesMode to default to the current release (which has been manually tracked in common.py for some time). This is how prepare has worked on Terra.
It also fixes --binariesMode to automatically switch to the GPU release as needed.
The usual environment variables, CACTUS_DOCKER_ORG, CACTUS_DOCKER_TAG, can still be used to override the image. The --latest option will still work, only it will point to the latest release rather than the latest commit.
If someone really wants to test a non-released commit with docker binaries, they will need to tag it themselves and use the environment variables.
When switching CI recently, I stopped it from spamming quay.io with a Cactus image for every single commit. This means that
--binariesMode dockerwill no longer work by default, since it will look for a commit-tagged image that isn't there.This PR switches
--binariesModeto default to the current release (which has been manually tracked incommon.pyfor some time). This is how prepare has worked on Terra.It also fixes
--binariesModeto automatically switch to the GPU release as needed.The usual environment variables,
CACTUS_DOCKER_ORG,CACTUS_DOCKER_TAG, can still be used to override the image. The--latestoption will still work, only it will point to the latest release rather than the latest commit.If someone really wants to test a non-released commit with docker binaries, they will need to tag it themselves and use the environment variables.