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

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

Re: grant me access on JIRA & Wiki

Hi Praveendra, I've added you to both the geode wiki and the geode JIRA. You might want to check out Geode's how to contribute page for some places to get started - https://cwiki.apache.org/confluence/display/GEODE/How+to+Contribute Thanks! -Dan On Tue, Apr 17, 2018 at 2:28 PM, Praveendra Sing

grant me access on JIRA & Wiki

I just created account to start contributing to Apache projects. Could you please grant me access on Jira & Wiki? fyi my github profile at https://github.com/pravsingh thank you. On Tue, Apr 17, 2018 at 2:18 PM, wrote: > > > Account signup > > You have signed up for a JIRA account at: > https

Failed: apache/geode#7521 (exclude-extensions-in-jar-check - 5372265)

Build Update for apache/geode - Build: #7521 Status: Failed Duration: 19 mins and 55 secs Commit: 5372265 (exclude-extensions-in-jar-check) Author: Bradford Boyle Message: Omit extensions in check of bundled jars [GEODE-5099] Signed-off-by Jianxia Chen View

Failed: apache/geode#7522 (exclude-extensions-in-jar-check - a8941fb)

Build Update for apache/geode - Build: #7522 Status: Failed Duration: 19 mins and 8 secs Commit: a8941fb (exclude-extensions-in-jar-check) Author: Bradford Boyle Message: Omit extensions in check of bundled jars [GEODE-5099] Signed-off-by Jianxia Chen View

Re: grant me access on JIRA & Wiki

forgot to mention that my user id is psinghiitr. thanks On Tue, Apr 17, 2018 at 2:28 PM, Praveendra Singh wrote: > I just created account to start contributing to Apache projects. > Could you please grant me access on Jira & Wiki? > > fyi my github profile at https://github.com/pravsingh > > >

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

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

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

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

Re: Geode 1.6.0

Thanks Mike. As a first-time release manager, you’ll need to add your key to the following locations: https://id.apache.org (add the fingerprint to your profile) https://github.com/apache/geode/blob/develop/KEYS https://dist.apache.org/repos/dist/release/geode/KEYS https://dist.apache.org/repos/

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

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

Re: Index on Region

XSD versions have always matched the version of the GemFire release. Starting with Geode 1.0, the XSD version was matched up with Geode release. So, for example, if we need to introduce a new XSD in Geode 1.7, then it should be named geode-1.7.xsd. On Tue, Apr 17, 2018 at 8:55 AM, John Blum wrote

Re: Index on Region

Well, the way I handle this in *Spring Data for Apache Geode* is, and to *Kirk's* point, the schema (XSD) version matches the SDG version. I.e. in SDG 2.0.0 [1] there is a spring-geode-2.0.0.xsd, and in SDG 2.1.0 [2] there now exists a spring-geode-2.1.0.xsd. So, you could have a cache-1.1.xsd, o

Re: Index on Region

but our xsd is versioned. If user wants to use a more "correct" xsd when they are creating a cache.xml file, should we allow them to reference a cache-2.0.xsd instead of cache-1.0.xsd? (provided that 2.0 is only a washed down version of 1.0, nothing new added). On Tue, Apr 17, 2018 at 8:28 AM, Mic

Re: Index on Region

Correct. We can "deprecate" any time we like as long as we have provided an alternative, but we should only "remove" on a major release. -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 Download the new GemFire book here.

Re: Index on Region

They way it works now is that our xsd, xml parser and xml generator are disconnected. The xsd file is only used by the xml editor when editing the xml. The parser is parsing everything allowed by xsd, but it's not generated by xsd. The XML generated by our generator is not validated using the xsd e

Re: Index on Region

Deprecation is a signal that a user should begin migrating to an alternative because that thing may be removed in a future release. Following the SemVer practice gives our users confidence that we won’t break stuff in a minor release. Anthony > On Apr 16, 2018, at 3:11 PM, Kirk Lund wrote: