Travis can pull authenticated docker images so GCR is usable. I'm not thrilled about a docker image that gets pushed to by a release process having a 'latest' tag that is not the same as the latest release artifact. We have a few options here:
1) Update travis to access GCR in an authenticated fashion. This leaves the dockerhub image alone. 2) Periodically generate a snapshot native-build image, push it to tag "snapshot" on dockerhub and don't update latest. This preserves functionality and doesn't require travis to possess any credentials. 3) Just overwrite latest at will. This implies that we don't actually care what latest is from a release standpoint so why are we pushing to it as part of a release at all? -Sean. On Mon, Feb 22, 2021 at 1:41 PM Jacob Barrett <jabarr...@vmware.com> wrote: > The original request was for access to update the docker image we have > been using for PRs and such. If you all want to discussion on doing > something different with its usage or where it is stored please start a new > thread. > > Mike, your image has been updated and all should be happy now. If you > still want access to do this yourself I don’t have the magic to make that > happen. > > -Jake > > > On Feb 22, 2021, at 1:28 PM, Owen Nichols <onich...@vmware.com<mailto: > onich...@vmware.com>> wrote: > > I don't believe LGTM uses it at all, but I do see that Travis is > configured to use "latest" tag. > > "latest" tag on apachegeode dockerhub is assumed to be a synonym for > "latest released version" (currently 1.13.1) > > If apachegeode dockerhub makes the most sense for hosting CI images, I > wonder if it could be as simple as using a different tag-naming scheme for > images that do not correspond to releases, maybe "latest-CI" or > "1.14.0-dev" or something? > > On 2/22/21, 12:12 PM, "Jacob Barrett" <jabarr...@vmware.com<mailto: > jabarr...@vmware.com>> wrote: > > Wherever we want to put it, if not dockerhub anymore, it must be > accessible by Travis and LGTM or we also stop using Travis and LGTM. > > On Feb 22, 2021, at 9:06 AM, Anthony Baker <bak...@vmware.com<mailto: > bak...@vmware.com>> wrote: > > Where are we hosting images for the geode (not the geode-native) > pipeline? While it might make sense to use the same repo across the board, > the images for geode-native and geode-site can be useful beyond just CI. I > know I use the geode-native-build image to vet releases. > > Anthony > > > On Feb 22, 2021, at 8:12 AM, Jacob Barrett <jabarr...@vmware.com<mailto: > jabarr...@vmware.com>> wrote: > > This docker image has been there for years and is not related to a release > but to the LGTM and Travis builds. I have access and can bump the image for > you Mike. > > -Jake > > On Feb 17, 2021, at 1:35 PM, Owen Nichols <onich...@vmware.com<mailto: > onich...@vmware.com>> wrote: > > apachegeode images on dockerhub correspond to releases. To make a change, > the change must first come to appropriate release branch, then a Geode > release made. > > Perhaps trying to use release images for CI is not quite the right > strategy? > > > --- > Sent from Workspace ONE Boxer< > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxer&data=04%7C01%7Cjabarrett%40vmware.com%7C3bc55f2d90fd4af5716b08d8d778ca5f%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637496261089330277%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qDuATku1EGJLtaZ%2BBcIgoSDwdeaAukL68sSY4A1Sjg8%3D&reserved=0 > > > > On February 17, 2021 at 1:24:04 PM PST, Mike Martell <marte...@vmware.com > <mailto:marte...@vmware.com>> wrote: > Please provide access to geode-native images on docker hub. Need to update > our latest docker image to support our new open source CI for geode-native. > In particular, need to upgrade to use cmake 3.18. > > Thanks, > Mike > >
