On Mon, Nov 19, 2018 at 10:36 AM Sage Weil <sweil@xxxxxxxxxx> wrote: > > iOn Fri, 16 Nov 2018, Alfredo Deza wrote: > > On Fri, Nov 16, 2018 at 3:37 PM Sage Weil <sweil@xxxxxxxxxx> wrote: > > > > > > What would it take to create container images for development builds > > > (i.e., ceph-ci branches)? > > > > > > Currently we don't need this for every branch, but it will be imporant > > > very soon (if it isn't already) to build images for some branches in order > > > to test changes targetting rook or ceph-ansible in container mode. IIRC > > > the issues are > > > > > > 1- we probably don't want to push a container for every ceph-ci build onto > > > docker hub, and we don't have a private container registry to push to > > > > This is the biggest hurdle IMO, we've tried in the past tinkering with > > a registry and it was just too complex (Dan or Ken might have better > > insight here). > > > > > > > > 2- jenkins isn't triggering a container build for dev builds > > > > > > 3- jenkins isn't triggering a container build for release builds either. > > > > Seems like this is already done and they are being pushed to docker hub: > > > > https://github.com/ceph/ceph-container/issues/1200 > > > > > > > > I'm guessing 3 is something we should just fix, so there's no human needed > > > to get an up to date container into the public registries after a release. > > > > Actually both 2 and 3 wouldn't be that hard, I do think that the > > registry is the biggest issue to tackle > > I wonder if we should just spam docker hub for now... I checked with the > gluster folks and that's what they're doing (albeit with a *much* smaller > image). As long as we push to a different image name or tag or something > so that it doesn't get confused with/mixed in with the real releases? Yeah, quay supports namespaces, so we could have "ceph-ci" or something.
