Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Owen Nichols
From: Jacob Barrett Sent: Monday, February 22, 2021 1:40 PM To: dev@geode.apache.org Subject: Re: Need Access to apachegeode/geode-native-build on docker hub The original request was for access to update the docker image we have been using for PRs and such. If you all want to

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Mike Martell
Thanks Jake. I'll roll back my temporary changes to Travis config as no longer needed. Mike From: Jacob Barrett Sent: Monday, February 22, 2021 1:40 PM To: dev@geode.apache.org Subject: Re: Need Access to apachegeode/geode-native-build on docker hub

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Sean Goller
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

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Jacob Barrett
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

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Owen Nichols
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

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Jacob Barrett
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 wrote: > > Where are we hosting images for the geode (not the geode-native) pipeline? > While it might make sense

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Robert Houghton
The apachegeode-ci pipeline is storing images on a GCR project aptly named "apachegeode-ci". It is currently a private repo, hosted on Google, paid by VMware. -Robert On 2/22/21, 9:06 AM, "Anthony Baker" wrote: Where are we hosting images for the geode (not the geode-native) pipeline?

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Anthony Baker
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

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-22 Thread Jacob Barrett
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 wrote: > > apachegeode images on dockerhub correspond to releases. To make a

Re: Need Access to apachegeode/geode-native-build on docker hub

2021-02-17 Thread Owen Nichols
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

Need Access to apachegeode/geode-native-build on docker hub

2021-02-17 Thread Mike Martell
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