You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Spring CI <ci...@spring.io> on 2016/04/15 22:34:18 UTC
[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #280 has
FAILED
-----------------------------------------------------------------------
Spring Data GemFire > Nightly-ApacheGeode > #280 failed.
-----------------------------------------------------------------------
Scheduled
No failed tests found, a possible compilation error.
https://build.spring.io/browse/SGF-NAG-280/
---------------------
Currently Responsible
---------------------
No one is responsible for fixing this build.
--------------
Failing Jobs
--------------
- Default Job (Default Stage): No tests found.
--
This message is automatically generated by Atlassian Bamboo
Re: [Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #280 has FAILED
Posted by John Blum <jb...@pivotal.io>.
The version (and branch) of SDG with Apache Geode support does not and
should not be changed until an actual, official release is made based on
Apache Geode 1.0.0-incubating.M2. The SDG release supporting Apache Geode
1.0.0-incubating.M2 cannot happen until Apache Geode 1.0.0-incubating.M2 is
available from Maven Central. Only once SDG 1.7.0.APACHE-GEODE-EA-M2 (with
support for Geode 1.0.0-incubating.M2) has be released and pushed can the
version support for Apache Geode be bumped to the M3 build snapshot.
I am well aware of this and monitoring the progress of the Apache Geode M2
release.
On Fri, Apr 15, 2016 at 1:50 PM, Anthony Baker <ab...@pivotal.io> wrote:
> Good catch! Yes, it should point at 1.0.0-incubating.M3-SNAPSHOT as that
> is the latest version.
>
> Anthony
>
> > On Apr 15, 2016, at 1:40 PM, Dan Smith <ds...@pivotal.io> wrote:
> >
> >
> > I think maybe this spring CI build should also probably be going after
> > *M3*-snapshot
> > now, not M2, because we've rolled the version on develop.
>
>
--
-John
503-504-8657
john.blum10101 (skype)
Re: [Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #280 has FAILED
Posted by Anthony Baker <ab...@pivotal.io>.
Good catch! Yes, it should point at 1.0.0-incubating.M3-SNAPSHOT as that is the latest version.
Anthony
> On Apr 15, 2016, at 1:40 PM, Dan Smith <ds...@pivotal.io> wrote:
>
>
> I think maybe this spring CI build should also probably be going after
> *M3*-snapshot
> now, not M2, because we've rolled the version on develop.
Re: [Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #280 has FAILED
Posted by Dan Smith <ds...@pivotal.io>.
This failed getting the M2 snapshot. It looks like maybe
repository.apache.org is down - at least I can't hit it with a browser
either.
I think maybe this spring CI build should also probably be going after
*M3*-snapshot
now, not M2, because we've rolled the version on develop.
-Dan
On Fri, Apr 15, 2016 at 1:34 PM, Spring CI <ci...@spring.io> wrote:
>
> -----------------------------------------------------------------------
> Spring Data GemFire > Nightly-ApacheGeode > #280 failed.
> -----------------------------------------------------------------------
> Scheduled
> No failed tests found, a possible compilation error.
>
> https://build.spring.io/browse/SGF-NAG-280/
>
> ---------------------
> Currently Responsible
> ---------------------
>
> No one is responsible for fixing this build.
>
>
>
> --------------
> Failing Jobs
> --------------
> - Default Job (Default Stage): No tests found.
>
>
>
>
> --
> This message is automatically generated by Atlassian Bamboo