Re: Release 1.8.0 pipeline issue

https://github.com/apache/geode/pull/2865 fixes this. Patrick or Helena will take point on getting it reviewed and merged tomorrow. > On Nov 15, 2018, at 2:08 PM, Jianxia Chen wrote: > > It sounds like we shouldn't have this job in the pipeline at

Re: November 2018 Board Report Final Draft

Board report has been posted, thanks Robert! --Mark On Wed, Nov 14, 2018 at 10:00 AM Robert Houghton wrote: > Here is the final form our report for the quarter. If it passes muster, can > someone commit it to the Apache repository for me? > > ## Description: > > > > Apache Geode provides a

Re: Release 1.8.0 pipeline issue

It sounds like we shouldn't have this job in the pipeline at all, since we only publish snapshots for the community on develop (and not release branches). I suggest you ignore it for now, and Patrick said he would look into deleting it properly tomorrow. On Thu, Nov 15, 2018 at 10:47 AM Alexander

Re: [DISCUSS] - Create new repository for geode benchmarks

+1, never thought there was any other option... On 11/15/18 10:47, Dan Smith wrote: Hi all, We (Naba, Sean, Brian and I) would like to add some benchmarks for geode, with a goal of eventually running them as part of our concourse build and detecting performance changes. We think it makes

Re: [DISCUSS] - Create new repository for geode benchmarks

+1 I think a separate repo makes sense, and I'm excited for this effort! On Thu, Nov 15, 2018 at 10:47 AM Dan Smith wrote: > Hi all, > > We (Naba, Sean, Brian and I) would like to add some benchmarks for geode, > with a goal of eventually running them as part of our concourse build and >

[DISCUSS] - Create new repository for geode benchmarks

Hi all, We (Naba, Sean, Brian and I) would like to add some benchmarks for geode, with a goal of eventually running them as part of our concourse build and detecting performance changes. We think it makes sense to put these benchmarks in a separate geode-benchmarks repository. That will make

Release 1.8.0 pipeline issue

Hi community, With the fix that Owen contributed the build on the 1.8.0 release pipeline is passing. However, the PublishArtifacts job is failing with the below error: > > Failed to publish publication 'maven' to repository 'maven' > >

Requesting access to concourse.

Hi, Please grant me access to the concourse infrastructure to run/setup pipelines. Regards Nabarun Nag