Hi team, I found that recent builds from Travis CI just goes pending nearly 1 day. I heard that Travis has max concurrent builds for given account and Apache project all uses same account. And also many Apache projects set up Travis CI. https://travis-ci.org/apache
Zeppelin seemed to apply a bright idea which utilizes PR author's Travis account. Might be better to look more, but it seems to require all contributors to sign up Travis CI and set build for their forked repo. I'm not sure we are OK for this. Another approach is moving our build CI to ASF Jenkins. I remember that why we didn't use ASF Jenkins is for precondition of multi-lang (requires Python, Ruby, NodeJS installed). We actually got rid of multi-lang tests, so it's cleared for now. Recently added Integration tests might not work well with ASF Jenkins though, but essential tests are more important than integration tests. It would be amazing if someone or company supports build machine (like Spark) so that we can have our own CI. It may be able to support rebuild, and we can even require PR to pass tests. (Zeppelin approach could also do this, since PR author can trigger rebuild for his/her PR build.) What do you think? Thanks, Jungtaek Lim (HeartSaVioR)
