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
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"
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
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
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
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
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
+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
+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]
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?
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
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
12 matches
Mail list logo
