We should start building a publishing Docker images automatically from GitHub actions, to make the release process quicker. Note that the we are actually already building the images as part of the CI, so this is just a matter of also configuring how to push them to DockerHub. Also, we should publish images only when a tag is pushed to the repository (i.e. a new version is released).
Possible blocking issue: to publish images to DockerHub we would need to use a personal token, as it is not possible to create tokens limited to a single organisation. This is not ideal from a security point-of-view, as that token could be used to also publish images under the "personal namespace" of the user who owns the token. A possible solution is to start using CERN's registry instead of (or in parallel to) DockerHub.
Currently, docker images are built and published somewhat manually, with the help of
reana-dev. See the wiki page https://github.com/reanahub/reana/wiki/Releasing for more details.We should start building a publishing Docker images automatically from GitHub actions, to make the release process quicker. Note that the we are actually already building the images as part of the CI, so this is just a matter of also configuring how to push them to DockerHub. Also, we should publish images only when a tag is pushed to the repository (i.e. a new version is released).
Possible blocking issue: to publish images to DockerHub we would need to use a personal token, as it is not possible to create tokens limited to a single organisation. This is not ideal from a security point-of-view, as that token could be used to also publish images under the "personal namespace" of the user who owns the token. A possible solution is to start using CERN's registry instead of (or in parallel to) DockerHub.