Re: [DISCUSS] CI improvements

2017-11-02 Thread Sean Goller
precheckin is literally './gradlew build :geode-assembly:acceptanceTest integrationTest distributedTest flakyTest' :) -S. On Thu, Nov 2, 2017 at 1:10 PM, Dan Smith wrote: > On Thu, Nov 2, 2017 at 11:58 AM, Sean Goller wrote: > > > Given the length of

Re: [DISCUSS] CI improvements

2017-11-02 Thread Dan Smith
On Thu, Nov 2, 2017 at 11:58 AM, Sean Goller wrote: > Given the length of time precheckin seems to run, would it make sense to > break it up? > > -Sean. > Sure, as long as we don't miss anything :) -Dan

Re: [DISCUSS] CI improvements

2017-11-02 Thread Sean Goller
Given the length of time precheckin seems to run, would it make sense to break it up? -Sean. On Thu, Nov 2, 2017 at 11:49 AM, Dan Smith wrote: > Looks good. Should we go ahead and change this to run precheckin instead of > build? > > -Dan > > On Thu, Nov 2, 2017 at 9:53 AM,

Re: [DISCUSS] CI improvements

2017-11-02 Thread Dan Smith
Looks good. Should we go ahead and change this to run precheckin instead of build? -Dan On Thu, Nov 2, 2017 at 9:53 AM, Anthony Baker wrote: > If you’d like to check this out, here’s the PR containing the pipeline and > job scripts: >

Re: [DISCUSS] CI improvements

2017-11-02 Thread Anthony Baker
If you’d like to check this out, here’s the PR containing the pipeline and job scripts: https://github.com/apache/geode/pull/1006 And the pipeline itself: https://concourse.apachegeode-ci.info There are three pipelines defined: - develop: runs `gradle build`. Can be extended to include other

Re: [DISCUSS] CI improvements

2017-10-06 Thread Anthony Baker
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

Re: [DISCUSS] CI improvements

2017-10-06 Thread Mark Bretl
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

2017-10-06 Thread Kenneth Howe
+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

2017-10-06 Thread Udo Kohlmeyer
+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

2017-10-06 Thread Jianxia Chen
+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

2017-10-06 Thread Jared Stewart
+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

2017-10-06 Thread Kirk Lund
+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

2017-10-06 Thread Jinmei Liao
+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

2017-10-06 Thread Gregory Chase
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

2017-10-06 Thread Anthony Baker
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