Geode unit tests completed in 'release-1.6.0/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/12

Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/301

Re: Volunteer for ASF Board report?

Correction, the due date is 5/9. > On Apr 25, 2018, at 11:33 AM, Anthony Baker wrote: > > Hi we need to submit a report on the Geode project to the ASF Board. Any > volunteers to take this up? > > The report is due 5/2 and should be drafted for community review a few days > prior to that.

Errored: apache/geode-examples#217 (release/1.6.0 - 45d174a)

Build Update for apache/geode-examples - Build: #217 Status: Errored Duration: 2 mins and 2 secs Commit: 45d174a (release/1.6.0) Author: Mike Stolz Message: Adding Mikes keys and changing version to 1.6.0 View the changeset: https://github.com/apache/geode-ex

Re: [Discuss] Scope of the CacheElement interface with the respect to the public cluster configuration API

Again, my concern is with documentation and direction, not necessarily going through and making these changes at right now. On Wed, Apr 25, 2018 at 3:45 PM, Jinmei Liao wrote: > Any config object that needs to be Identifiable and Serializable should be > identified as a CacheElement, but we don'

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #898 was SUCCESSFUL (with 2376 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #898 was successful. --- Scheduled 2378 tests in total. https://build.spring.io/browse/SGF-NAG-898/ -- This

Re: [Discuss] Scope of the CacheElement interface with the respect to the public cluster configuration API

Any config object that needs to be Identifiable and Serializable should be identified as a CacheElement, but we don't have to go through all of the objects and identify them at once. When we are refactoring each individual commands and recognize the need, we will identify the object to be a CacheEl

Re: [Discuss] Scope of the CacheElement interface with the respect to the public cluster configuration API

Sorry, I forgot to step away from the In The Weeds where I am. o.a.g.cache.configuration.CacheElement is the experimental interface meant to identify an extension's configuration classes for consumption with the new cluster configuration interface. Extension developers can then use the configurat

Re: [Discuss] Scope of the CacheElement interface with the respect to the public cluster configuration API

It looks like there are two classes called CacheElement in the codebase; am I correct in thinking that you're referring to org.apache.geode.cache.configuration.CacheElement? This class doesn't have a Javadoc, so it's a little hard as an outsider to understand exactly what it is or how it's use

Volunteer for ASF Board report?

Hi we need to submit a report on the Geode project to the ASF Board. Any volunteers to take this up? The report is due 5/2 and should be drafted for community review a few days prior to that. Thanks, Anthony