[GitHub] geode issue #367: GEODE-2370: First pass at a CONTRIBUTING document.

2017-01-28 Thread pivotal-jbarrett
Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/367 We should include links to CTest documents. To run singles or subsets of tests you need to use ctest directly. ctest -R --- If your project is set up for it, you can

[jira] [Commented] (GEODE-2370) Need to create a CONTRIBUTING.md

2017-01-28 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15844073#comment-15844073 ] ASF GitHub Bot commented on GEODE-2370: --- Github user pivotal-jbarrett commented on t

Build failed in Jenkins: Geode-nightly #730

2017-01-28 Thread Apache Jenkins Server
See Changes: [hkhamesra] updated version number to 1.2.0 in gradle.properties. [kduling] GEODE-2298: Executing a Function via Swagger without parameters throws [kduling] GEODE-2294: When attempting to execute a function via Dev Rest API,

[GitHub] geode pull request #370: Feature/geode 2351

2017-01-28 Thread mmartell
GitHub user mmartell opened a pull request: https://github.com/apache/geode/pull/370 Feature/geode 2351 You can merge this pull request into a Git repository by running: $ git pull https://github.com/mmartell/geode feature/GEODE-2351 Alternatively you can review and apply the

Re: The next release (v1.1.0)

2017-01-28 Thread Michael Stolz
Yay! +1 -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Fri, Jan 27, 2017 at 6:40 AM, Anthony Baker wrote: > Looks like all the JIRA’s for v1.1.0 have been wrapped up [1]. I say > let’s cut a release branch and move ahead. > > Anthony > > [1] https://issues.a

Fwd: Build failed in Jenkins: Geode-release #39

2017-01-28 Thread Anthony Baker
Looks like some lucene tests are failing on the release branch. Anthony > Begin forwarded message: > > From: Apache Jenkins Server > Subject: Build failed in Jenkins: Geode-release #39 > Date: January 27, 2017 at 11:01:59 PM PST > To: dev@geode.apache.org > Reply-To: dev@geode.apache.org > >

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #453 has FAILED (11 tests failed, no failures were new)

2017-01-28 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #453 failed. --- Scheduled 11/1666 tests failed, no failures were new. https://build.spring.io/browse/SGF-NAG-453