Re: [DISCUSS] Scaling out CI capability

ZEPPELIN-2123 is resolved. Pull requests build capacity is not limited by 5 concurrent build any more. Now Zeppelin project leverages each individual contributors travis-ci, so we've got virtually unlimited concurrent build capacity for pull request. Only thing the contributor should aware is

Re: [DISCUSS] Scaling out CI capability

Thanks for the feedbacks! Then let me merge https://github.com/apache/zeppelin/pull/2026 and configure Jenkins for building PR. Worst case, If something does not work, then we can just come back to travis build PR with almost no effort. I'll update progress in the issue comment

Re: [DISCUSS] Scaling out CI capability

I think it's good idea. :-) On Thu, Feb 16, 2017 at 7:54 PM, Jeff Zhang wrote: > Great, can't wait to try this. > > > > moon soo Lee 于2017年2月16日周四 下午6:35写道： > > > Hi Apache Zeppelin contributors! > > > > Recently, it's not very difficult to see pullrequest is

Re: [DISCUSS] Scaling out CI capability

Great, can't wait to try this. moon soo Lee 于2017年2月16日周四 下午6:35写道： > Hi Apache Zeppelin contributors! > > Recently, it's not very difficult to see pullrequest is waiting more than > 10 hours to get travis-ci build slot. > > It's because of all ASF project shares the same

[DISCUSS] Scaling out CI capability

Hi Apache Zeppelin contributors! Recently, it's not very difficult to see pullrequest is waiting more than 10 hours to get travis-ci build slot. It's because of all ASF project shares the same travis account and the account's capability is limited. Although ASF assigned 5 concurrent build