beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2878) Release process for container images
Date Wed, 11 Oct 2017 22:05:00 GMT


ASF GitHub Bot commented on BEAM-2878:

GitHub user herohde opened a pull request:

    [BEAM-2878] Use bintray as default for container images

    R: @kennknowles 

You can merge this pull request into a Git repository by running:

    $ git pull containers

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3981
commit ee2408b9b0637d2876f246ac1acb7d358d5ddc71
Author: Henning Rohde <>
Date:   2017-10-11T21:52:28Z

    [BEAM-2878] Use bintray as default container images


> Release process for container images
> ------------------------------------
>                 Key: BEAM-2878
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Henning Rohde
>            Assignee: Kenneth Knowles
>              Labels: portability
> We need to push container images -- notably SDK harness container images -- to a public
place with each release, so that they can be referenced and used. For example,
might be an option, although Docker hub seems more geared towards containerizing container-unware
content post-release.
> For users who wish to build dev (or custom) container images any location is fine (personal
account on docker hub, GCR, etc), but we do not want it to be a requirement for normal use
of official Beam releases.

This message was sent by Atlassian JIRA

View raw message