infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning Rohde (JIRA)" <>
Subject [jira] [Commented] (INFRA-15382) Snapshot docker repo for Beam project
Date Thu, 02 Nov 2017 00:06:00 GMT


Henning Rohde commented on INFRA-15382:

Let me try to clarify what we're doing: as part of each build, we produce docker container
images. They are part of the release, includes intermediate content and are needed to test
and verify other artifacts. They are notably _not_ built as a 2nd independent step, which
is what dockerhub automated builds are about (= dockerizing docker-unaware bits). Maintaining
a set of Dockerfiles on dockerhub or in a separate beam git repository would work very poorly
for us. This document describes how we build them:

For releases, the plan is to push these images to the repo here:
It is already created. Images here are part of the official Beam releases.

For daily "snapshot" builds, we want to push the container images to a similar, but different,
repo on, say, "beam-snapshots-docker". Although we could just distinguish non-release
images by tags, we prefer a different repo to ensure that (a) released container images are
not accidentally modified or deleted by the daily build process; and (b) users are unlikely
to mistake a non-release (unsupported) image with a released (supported) image. This JIRA
is requesting that this repo is created.

> Snapshot docker repo for Beam project
> -------------------------------------
>                 Key: INFRA-15382
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Other/Misc
>            Reporter: Kenneth Knowles
>            Assignee: Chris Lambertus
>            Priority: Major
> This ticket is a follow up on INFRA-15256, in which Beam gained a {{beam-docker}} repo
(base URL {{}} for pushing containers) to be used by our
official releases.
> What we also need is a place to push containers for release candidates, etc. This should
be impossible to mistake for a release, so that users do not find them and they adhere to
ASF releasing policies.
> I think it makes sense to have separate {{beam-docker-snapshots}} repo to match the way
that we have a separate Nexus snapshot repo. We would like to be able to push snapshots from
Jenkins, just as we {{mvn deploy}} nightlies/release candidates.

This message was sent by Atlassian JIRA

View raw message