Closed abesto closed 9 years ago
LGTM thanks for streamlining things. We'll need to warn users about the repo change until we have a process down to push "major" versions to dockerhub.
Closing this, will open another PR where the process is automated.
Why
1.4.0-quay.io
was just pushed") to re-build in case of intermittent failures, while Docker Hub UI only supports triggering all the build configurations.quay.io/opnezipkin/zipkin-collector:1.4.0
instead ofopenzipkin/zipkin-collector:1.4.0
How
Docker Hub supports dependent builds but doesn't support automatic docker tags from git tags. Quay.io supports automatic docker tags, but not dependent builds. We use the former to simulate the latter by starting
zipkin-base
with tags likebase-1.4.0
, and buildingFROM
that tag in the other images; the images to be used by our users will still be versioned normally, with tags like1.4.0
.Example
By pushing
base-1.4.0
I started thiszipkin-base
build, creating the docker tagbase-1.4.0
onzipkin-base
. Then I updated theDockerfile
s and pushed the tag1.4.0-quay.io
(if we choose to migrate, we'd of course drop the qualifier). This started builds for the rest of the services, creating the docker tag1.4.0-quay.io
, like here.