Bug #16565

Updated by Peter Amstutz almost 2 years ago

Currently the script to build arvados/jobs either has an explicit version (for stable builds) or it determines the arvados-cwl-runner version and tags it as both that version and "latest".

We should not push development versions as "latest".

From discussion: Latest should be latest stable, or we shouldn't have any "latest" tag at all. Ensure the build pipeline works without assuming "latest".

Separately: workbench submits workflows using the "latest" tag, but really this should match the version of the cluster that is installed.