Use explicit releases to push to Docker Hub, rather than pushing every update to master

ros-tooling / setup-ros-docker

2 stars 5 forks source link

Use explicit releases to push to Docker Hub, rather than pushing every update to master #26

Closed emersonknapp closed 3 years ago

emersonknapp commented 3 years ago

Description

When a new change is checked in, we immediately overwrite the dockerhub images with the newest one. This doesn't allow any ability to "bake-in" these changes, with no good options for a user to roll back on their end.

Instead, we should:

push master as a -preview-tagged image
push latest explicit release as a -latest-tagged image

This will allow us to experimentally use the preview image from other repositories and try it out before releasing

emersonknapp commented 3 years ago

Maybe the real answer is to have a few test cases to check for regressions before pushing to dockerhub