Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CA+F1uf=h+j8ZoQidgRBJDgV2sH0_w2V3-o1BFyQxrP_x6niQ7Q@mail.gmail.com>
References: <CAOPnHqdkXpmx25dMUSrbEBeySXdr1rbArrcBnccLuCx+iMbCJg@mail.gmail.com>
 <CA+F1uf=h+j8ZoQidgRBJDgV2sH0_w2V3-o1BFyQxrP_x6niQ7Q@mail.gmail.com>
From: Ming Li <mli@pivotal.io>
Date: Fri, 24 Jun 2016 16:43:55 +0800
Message-ID: <CA+F1ufnHfExXd9Wpcgts1JxEOsUOXCmatojkOdYx38x_oZ14yg@mail.gmail.com>
Subject: Re: Use Travis instead of Jenkins to ensure building success from
 pull request?
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11419b3ec2b6140536022bc8
archived-at: Fri, 24 Jun 2016 08:44:08 -0000

--001a11419b3ec2b6140536022bc8
Content-Type: text/plain; charset=UTF-8

Moreover, we can put other simple build processes onto free github
integrated services.

E.g. after enable travis_ci, we can enable Coverity Scan build (
https://scan.coverity.com/travis_ci) further.

More free services can be exploited (like Coverage report build), we need
to investigate how to use them.

On Fri, Jun 24, 2016 at 4:17 PM, Ming Li <mli@pivotal.io> wrote:

> Agree.
>
> BTW, one more problem: Now we only have Jenkins for testing pull
> requests, but we don't test against the latest code on branch master.
> And also it is better to keep monitor on the building status on main page
> at https://github.com/apache/incubator-hawq, so that we can easily found
> building error.
>
> On Fri, Jun 24, 2016 at 3:06 PM, hong wu <xunzhangthu@gmail.com> wrote:
>
>> Hi HAWQ committers,
>>
>> Recently, since the Jenkins service integrated inside apache HAWQ project
>> is problematic, could we open the travis service instead? The .travis.yml
>> file
>> has already existed and has worked in self-forked HAWQ repos(such as
>> https://travis-ci.org/xunzhang/incubator-hawq/builds). The original
>> Jenkins
>> script was something wrong and even didn't check compiling.
>>
>> Some pros:
>>  - Travis CI script is visible to developers/users which is much more
>> friendly and easier to maintain(comparing to Jenkins)
>>  - To make sure every pull request is valid(comparing to current status)
>>
>> Some cons:
>>  - Admin could not log into the Travis machine to debug.
>>  - Current travis script only check building status in osx. Because of the
>> osx resource in travis machine is limited: some pending time + not that
>> enough CPUs. It will take about 25min to pass the total HAWQ building
>> process.
>>
>> Also, I am not sure whether A apache project must use Jenkins for its
>> open-source CI. Any comments? Thanks.
>>
>> Best
>> xunzhang
>>
>
>

--001a11419b3ec2b6140536022bc8--