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" <marte...@vmware.com> wrote:
Thanks Jake. I'll roll back my temporary changes to Travis config as no
longer needed.
Mike
________________________________
From: Jacob Barrett <jabarr...@vmware.com>
Sent: Monday, February 22, 2021 1:40 PM
To: dev@geode.apache.org <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
<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%7Conichols%40vmware.com%7C1662346761564125865a08d8d786e5fe%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637496321676712117%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=tlMtlPGI9tvctCfBLTxbYF7r6SH2oi2zxBsB28rJCLI%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
