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 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
> 
> On February 17, 2021 at 1:24:04 PM PST, Mike Martell  
> 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

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 22, 2021, at 8:12 AM, Jacob Barrett  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  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
>> 
>> On February 17, 2021 at 1:24:04 PM PST, Mike Martell  
>> 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
>

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?  
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  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  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
>> 
>> On February 17, 2021 at 1:24:04 PM PST, Mike Martell 
 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
>

Re: [Suspected Spam] [VOTE] Apache Geode 1.12.1.RC4

2021-02-22 Thread Donal Evans 
+1

Verified that no regressions in performance were present compared to previous 
versions using some private performance tests. Everything looks good!

From: Owen Nichols 
Sent: Sunday, February 21, 2021 12:07 PM
To: dev@geode.apache.org 
Subject: [Suspected Spam] [VOTE] Apache Geode 1.12.1.RC4

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.12.1.RC4.
Thanks to all the community members for their contributions to this release!

Please do a review and give your feedback, including the checks you performed.

Voting deadline:
3PM PST Thu, February 25 2021.

Please note that we are voting upon the source tag:
rel/v1.12.1.RC4

Release notes:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.12.1&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807684447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=449EWxP6TrW77Q%2FrBUyRdct54gPs%2B4SkSwEBV57qyjo%3D&reserved=0

Source and binary distributions:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.12.1.RC4%2F&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807684447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fYaFDL%2BdbNIrejCt0OnCp8WfNa9MO1dSvdAKve%2FLo%2Bo%3D&reserved=0

Maven staging repo:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1075&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807684447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FZF8F%2FOW9nQqcEOlnNyQ3bUKPf4zSyamVuDTkhUJOvM%3D&reserved=0

GitHub:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807684447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=H1jixeRDcqaA8gsS0%2F2tGHO10eaZPPm8zSGomCIuV8o%3D&reserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807694447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=g%2Berl3o%2FGdIkvkmcKrgP3bv49GBFi2D8CeswopKovgc%3D&reserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807694447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VHc7CyQAUPhRMG%2BrFE2a2aMcs6XyDpcMtkHkrfDHTUU%3D&reserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-benchmarks%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807694447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Eoa0I12Zd8kB8socErFsd6SNHOWwSoGXnPDCHvLshTk%3D&reserved=0

Pipelines:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-main&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807694447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YLhmB77FkA5mQFuykkiKvEOuSGO6e%2Bcw5RQtKK0lgUU%3D&reserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-rc&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348807694447%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OZSUrRMHEo%2BjtsdDvMLbkewtsCUHAzxttzbi%2Fuiohvo%3D&reserved=0

Geode's KEYS file containing PGP keys we use to sign the release:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fblob%2Fdevelop%2FKEYS&data=04%7C01%7Cdoevans%40vmware.com%7C9e9f4072c4b54d9b719b08d8d6a46285%7Cb39138ca3cee4b4aa4d6cd83d9

Re: [VOTE] Apache Geode 1.12.1.RC4

2021-02-22 Thread Robert Houghton 
+1

I verified the version.properties file contents to match the pipeline version 
that we've tested and verified.
-Robert Houghton


On 2/21/21, 12:08 PM, "Owen Nichols"  wrote:

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.12.1.RC4.
Thanks to all the community members for their contributions to this release!

Please do a review and give your feedback, including the checks you 
performed.

Voting deadline:
3PM PST Thu, February 25 2021.

Please note that we are voting upon the source tag:
rel/v1.12.1.RC4

Release notes:

https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.1

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.12.1.RC4/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1075

GitHub:

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Crhoughton%40vmware.com%7Cf221b519b16b4ebf161008d8d6a46188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637495348793363365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yBvhGM48yiWnZ0Gz3Q9mI%2B3J2ddoAoBGh4Oi3Jmo1Mw%3D&reserved=0

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Crhoughton%40vmware.com%7Cf221b519b16b4ebf161008d8d6a46188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637495348793363365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=92jZ7B2TeRyIUgcHSToUKC8sW%2Bh%2BRRt8sSTMTAKS%2Fj0%3D&reserved=0

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Crhoughton%40vmware.com%7Cf221b519b16b4ebf161008d8d6a46188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637495348793363365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=tJ7gap56xlCUH7vlWzebu1bss%2BTRmBJMBM6AYZOrqKg%3D&reserved=0

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-benchmarks%2Ftree%2Frel%2Fv1.12.1.RC4&data=04%7C01%7Crhoughton%40vmware.com%7Cf221b519b16b4ebf161008d8d6a46188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637495348793363365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=b1aVxqH8Kynl9BkHk3%2Fgxin5GDNaxuP684sAtqy3zD0%3D&reserved=0

Pipelines:

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-main&data=04%7C01%7Crhoughton%40vmware.com%7Cf221b519b16b4ebf161008d8d6a46188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637495348793363365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=oeLPQLMuJYX3h%2FQTVex61x6s0jdaXywWJlWIgZU%2Ftzw%3D&reserved=0

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-rc&data=04%7C01%7Crhoughton%40vmware.com%7Cf221b519b16b4ebf161008d8d6a46188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637495348793363365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fLNXbsgn%2BuX44vumuIMB2mluKjb5Uz7k9%2BemWLcQH70%3D&reserved=0

Geode's KEYS file containing PGP keys we use to sign the release:

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fblob%2Fdevelop%2FKEYS&data=04%7C01%7Crhoughton%40vmware.com%7Cf221b519b16b4ebf161008d8d6a46188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637495348793363365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X%2BGCSmUWwk8INBHRgBFq0biDO58gZMcVtZRagPptByo%3D&reserved=0

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.12.1.RC4 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1075
 build runAll

Regards
Owen Nichols

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 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  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  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
>>> 
>>> On February 17, 2021 at 1:24:04 PM PST, Mike Martell  
>>> 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
>> 
>

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 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"  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  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  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  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
>>> 
>>> On February 17, 2021 at 1:24:04 PM PST, Mike Martell 
 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
>> 
>

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 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 
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" 
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 
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 
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 
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

On February 17, 2021 at 1:24:04 PM PST, Mike Martell 
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

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 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  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>> 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>> 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>> 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>> 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>> 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  > 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
>
>

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

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 
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" 
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 
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 
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 
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

On February 17, 2021 at 1:24:04 PM PST, Mike Martell 
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

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

2021-02-22 Thread Owen Nichols 
Trying to use the same tag for two incompatible purposes seems like an 
anti-pattern that could be easily avoided.  

Most dockerhub repos adhere to the convention that "latest" is an alias for the 
latest release tag (currently 1.13.1).  Something obviously un-release-like 
"latest-snapshot" might be a better tag name for the latest image needed for 
Travis CI for develop.  This would require a 1-line fix in .travis.yml:28

Please note that your manually-pushed changes to latest tag will be overwritten 
whenever a new Geode release is made (next either 1.13.2 or 1.14.0, whichever 
comes first -- and neither of those branch have the version of cmake develop 
needs). 

On 2/22/21, 3:09 PM, "Mike Martell"  wrote:

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

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 
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" 
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 
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 
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 
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

On February 17, 2021 at 1:24:04 PM PST, Mike Martell 
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

Fixed: apache/geode-native#3054 (develop - 679274d)

2021-02-22 Thread Travis CI 
Build Update for apache/geode-native
-

Build: #3054
Status: Fixed

Duration: 1 hr, 40 mins, and 0 secs
Commit: 679274d (develop)
Author: Michael Martell
Message: GEODE-8949 rollback travis config since docker image updated to lates… 
(#749)

* GEODE-8949 rollback travis config since docker image updated to latest cmake

* Fix clang-format error

View the changeset: 
https://github.com/apache/geode-native/compare/a5374926c75b...679274d37897

View the full build log and details: 
https://travis-ci.com/github/apache/geode-native/builds/217921704?utm_medium=notification&utm_source=email


--

You can unsubscribe from build emails from the apache/geode-native repository 
going to 
https://travis-ci.com/account/preferences/unsubscribe?repository=16807653&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.