On Tue, Aug 27, 2019 at 6:20 PM Ahmet Altay <[email protected]> wrote: > > On Tue, Aug 27, 2019 at 5:50 PM Robert Bradshaw <[email protected]> wrote: >> >> On Tue, Aug 27, 2019 at 3:35 PM Hannah Jiang <[email protected]> wrote: >> > >> > Hi team >> > >> > I am working on improving docker container support for Beam. We would like >> > to publish prebuilt containers for each release version and daily >> > snapshot. Current work focuses on release images only and it would be part >> > of the release process. >> >> This would be great! >> >> > The release images will be pushed to GCR which is publicly >> > accessible(pullable). We will use the following locations. >> > Repository: gcr.io/beam >> > Project: apache-beam-testing >> >> Given that these are release artifacts, we should use a project with >> more restricted access than "anyone who opens a PR on github." > > > We have two options: > - gcr.io works based on the permissions of the gcs bucket that is backing > it. GCS supports bucket only permissions. These permissions needs to be > explicitly granted and the service accounts used by jenkins jobs does not > have these explicit permissions today. > - we can create a new project in gcr, bintray or anything else that offers > the same service.
I think the cleanest is to simply have a new project whose membership consists of (interested) PMC members. If we have to populate this manually I think that'd still be OK as the churn is quite low.
