Hi Roman, Do you have the admin privilege of hawq on githup? If not, could you please help me to forward this email to the right person? We need to take some actions on githup setting to trigger travis_ci and Coverity Scan. Thanks.
On Tue, Jun 28, 2016 at 1:24 PM, Jiali Yao <[email protected]> wrote: > @Hong, thanks for your comments. > For 1, Ubuntu can be integrated. Thought? > For 2, Since the time is related to resource and CPU, it is not stabled > every time. But I do not think it is blocked so far. > > Thanks > Jiali > > > On Mon, Jun 27, 2016 at 11:16 AM, hong wu <[email protected]> wrote: > > > @Jiali, see my comments inline below: > > > > 1. Beside MAC build, should we add other platform builds such as Redhat? > > > Travis CI only supports ubuntu for Linux( > > > https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments > > ). > > Does it make sense integrating HAWQ build in Ubuntu? > > 2. About building time, is it possible that we figure out ways that we > can > > make it quick. 25 mins seems a little long. > > > Actually I didn't optimize the build time yet and it is possible to > make > > it faster. What time is suitable, 20 mins? > > > > Thanks > > > > 2016-06-27 10:50 GMT+08:00 Jiali Yao <[email protected]>: > > > > > Great point to have more test in Apache CI. > > > While I want to add some comments > > > 1. Beside MAC build, should we add other platform builds such as > Redhat? > > > 2. About building time, is it possible that we figure out ways that we > > can > > > make it quick. 25 mins seems a little long. > > > > > > Thanks > > > Jiali > > > > > > > > > On Fri, Jun 24, 2016 at 4:43 PM, Ming Li <[email protected]> wrote: > > > > > > > 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 <[email protected]> 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 <[email protected]> > > > 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 > > > > >> > > > > > > > > > > > > > > > > > > > >
