infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15382) Snapshot docker repo for Beam project
Date Wed, 01 Nov 2017 13:27:02 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234063#comment-16234063
] 

Kenneth Knowles commented on INFRA-15382:
-----------------------------------------

Yes, for Beam, we definitely need generalized access. The permissions granted on INFRA-14586
seem like they would work. I had been working from comments on INFRA-12781 that were a bit
more strict and would not grant the capabilities we need. So I pursued a docker registry on
bintray (resolved as part of INFRA-15256) for released images, I believe analogous to maven
central for jars or pypi for eggs, in terms of their relation to ASF distribution policy.

This ticket's request is to have a second docker registry with generalized access and that
our CI builds can push to, as with https://repository.apache.org/snapshots/org/apache/beam.
I believe we can use it also for staging release candidates analogous to e.g. https://repository.apache.org/content/repositories/orgapachebeam-1022/

It is definitely not for releases, and we will definitely document and disclaim that this
is not an official distribution channel. Is there a preference for dockerhub over bintray
for images that are not official releases?

> Snapshot docker repo for Beam project
> -------------------------------------
>
>                 Key: INFRA-15382
>                 URL: https://issues.apache.org/jira/browse/INFRA-15382
>             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 {{apache-docker-beam-docker.bintray.io}} 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.
> WDYT?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message