[DISCUSS] CodeClimate analysis of Geode

Hi everyone, I set up my fork of Geode with CodeClimate to see if the tool might get us interesting information. You can see the results here The current configuration of CodeClimate uses PMD (https://pmd.github.io/) with the *Basic, Code

Failed: jinmeiliao/geode#30 (gem-1691 - 274b439)

Build Update for jinmeiliao/geode - Build: #30 Status: Failed Duration: 12 minutes and 46 seconds Commit: 274b439 (gem-1691) Author: Jinmei Liao Message: GEODE-3785: correctly update the schema version, namespace and lcoation when importing old schema View

Broken: apache/geode#4200 (develop - d1ef591)

Build Update for apache/geode - Build: #4200 Status: Broken Duration: 7 minutes and 16 seconds Commit: d1ef591 (develop) Author: Jens Deppe Message: GEODE-3746: FunctionCommandsDUnitTest uses http as transport View the changeset:

Build failed in Jenkins: Geode-nightly-flaky #141

See Changes: [jdeppe] GEODE-3542: Add descriptive error message for gfsh show metrics [jdeppe] GEODE-3542: Increase await timeout to 2 minutes in case of long GCs on [boglesby] GEODE-3730: Moved retry logic

Re: [DISCUSS] CI improvements

Comments inline > On Oct 6, 2017, at 11:51 AM, Mark Bretl wrote: > > Correct, there is no requirement from ASF about where to run CI or even to > run CI. I am all for the best tools and stable (and repeatable) > environments. I would be open to seeing how Concourse could

Build failed in Jenkins: Geode-nightly #976

See Changes: [boglesby] GEODE-3730: Moved retry logic to receiver when [boglesby] GEODE-3730: Moved retry loop around switch statement [eshu] GEODE-3744: Local region will not participate in a transaction hosted

Re: [DISCUSS] CI improvements

Correct, there is no requirement from ASF about where to run CI or even to run CI. I am all for the best tools and stable (and repeatable) environments. I would be open to seeing how Concourse could work for Geode. Once the Concourse environment is setup, probably would be best to update the

Re: [DISCUSS] CI improvements

+1 - Reduce the noise level for analyzing CI results > On Oct 6, 2017, at 9:49 AM, Udo Kohlmeyer wrote: > > +1 Switch... parallel runs would be safest > > On Fri, Oct 6, 2017 at 9:42 AM, Jianxia Chen wrote: > >> +1 to switch to Concourse >> +1 As a

Re: [DISCUSS] CI improvements

+1 Switch... parallel runs would be safest On Fri, Oct 6, 2017 at 9:42 AM, Jianxia Chen wrote: > +1 to switch to Concourse > +1 As a first step we could run both CI systems side-by-side and see how > the Concourse approach works for our project. > > On Fri, Oct 6, 2017 at

Re: [DISCUSS] CI improvements

+1 to switch to Concourse +1 As a first step we could run both CI systems side-by-side and see how the Concourse approach works for our project. On Fri, Oct 6, 2017 at 7:08 AM, Anthony Baker wrote: > Hi all, > > I’d like to propose the following that we switch our continuous

Re: [DISCUSS] CI improvements

+1 I think this will be a huge improvement to the reliability of our test infrastructure. - Jared > On Oct 6, 2017, at 9:26 AM, Kirk Lund wrote: > > +1 no thoughts other than make it so! > > On Fri, Oct 6, 2017 at 7:08 AM, Anthony Baker wrote: > >> Hi

Re: [DISCUSS] CI improvements

+1 no thoughts other than make it so! On Fri, Oct 6, 2017 at 7:08 AM, Anthony Baker wrote: > Hi all, > > I’d like to propose the following that we switch our continuous > integration (CI) system from Jenkins [1] to Concourse [2]. I suggest > this because we continue to

Re: [DISCUSS] CI improvements

+1 for switching concourse and running it side by side first to see how it works first. On Fri, Oct 6, 2017 at 7:57 AM, Gregory Chase wrote: > I recall hearing that Apache HAWQ already runs Concourse in a similar > approach. > > I also know of at least three other open source

Re: [DISCUSS] CI improvements

I recall hearing that Apache HAWQ already runs Concourse in a similar approach. I also know of at least three other open source projects are running Concourse: 1. Concourse.ci itself 2. Greenplum Database 3. RabbitMQ

[DISCUSS] CI improvements

Hi all, I’d like to propose the following that we switch our continuous integration (CI) system from Jenkins [1] to Concourse [2]. I suggest this because we continue to experience a significant number of environmental-related test failures. These issues include CPU interference from other