[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #918 was SUCCESSFUL (with 2398 tests). Change made by John Blum.

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #918 was successful.
---
Scheduled with changes by John Blum.
2400 tests in total.

https://build.spring.io/browse/SGF-NAG-918/




--
Code Changes
--
John Blum (b5fe5f8c8de4467a8fe99f54516d079cdec33394):

>DATAGEODE-105 - Add ability to filter types de/serialized by the 
>o.s.d.g.mapping.MappingPdxSerializer.



--
This message is automatically generated by Atlassian Bamboo

Re: Concourse infrastructure

[Alexander Murmann]

Thanks for your restless efforts to fix this!

On Tue, May 15, 2018 at 10:05 AM, Sean Goller  wrote:

> Update: We are back! Once a build makes it all the way through develop I'll
> enable the metrics pipeline.
>
> On Mon, May 14, 2018 at 9:12 PM, Sean Goller  wrote:
>
> > Update: The infrastructure is still messed up. I've been working on
> > bringing up a replacement infrastructure, but it's taking longer than
> > anticipated. Hopefully I'll be able to finish up in the morning.
> >
> > -S.
> >
> > On Mon, May 14, 2018 at 9:59 AM, Sean Goller  wrote:
> >
> >> Currently the concourse infrastructure is suffering from massive
> internal
> >> networking issues, we are working to resolve this as soon as possible.
> I'll
> >> update the community as we progress on the repair.
> >>
> >
> >
>

Re: Concourse infrastructure

[Sean Goller]

Update: We are back! Once a build makes it all the way through develop I'll
enable the metrics pipeline.

On Mon, May 14, 2018 at 9:12 PM, Sean Goller  wrote:

> Update: The infrastructure is still messed up. I've been working on
> bringing up a replacement infrastructure, but it's taking longer than
> anticipated. Hopefully I'll be able to finish up in the morning.
>
> -S.
>
> On Mon, May 14, 2018 at 9:59 AM, Sean Goller  wrote:
>
>> Currently the concourse infrastructure is suffering from massive internal
>> networking issues, we are working to resolve this as soon as possible. I'll
>> update the community as we progress on the repair.
>>
>
>