Re: Wish to hear your opinion on adopting public CI

[Kyle Nusbaum <kn...@yahoo-inc.com.INVALID>]

I've created an issue with the Apache Infrastructure guys for enabling Travis CI on our git repo.
https://issues.apache.org/jira/browse/INFRA-9511   -- Kyle
 


     On Thursday, March 26, 2015 5:23 PM, 임정택 <ka...@gmail.com> wrote:
   

 Yes, we should ask Apache Infra to set up Travis CI (with asfgit account),
which is not an issue cause many projects on Apache already uses Travis CI.
ex. https://issues.apache.org/jira/browse/INFRA-6161

I've just finished work about adopting Travis CI (with my fork), so we're
ready!
https://travis-ci.org/HeartSaVioR/storm/builds/56021889

Could any committers help requesting set up Travis CI to Apache Infra?

Btw, jira issue link is here,
https://issues.apache.org/jira/browse/STORM-704 and PR is here,
https://github.com/apache/storm/pull/486

Thanks in advance!

ps. Please note that Travis CI becomes too slow, and it actually runs mvn
install -DskipTests before build, so it takes some mins to assign VM and
boot, and another 10 ~ 15 mins to build for now.


2015-03-26 23:54 GMT+09:00 Bobby Evans <ev...@yahoo-inc.com.invalid>:

> I would love to see CI setup.  I don't know how Apache feels about
> travis-ci, we mostly ran into issues with setting up ruby on the jenkins
> nodes.  Now I am sure there will be issues with nodejs.  If travis-ci makes
> this simpler I would be all for using it.  But because it requires some
> github hooks we will need Apache Infra to help out setting it up.
>  - Bobby
>
>
>
>      On Wednesday, March 25, 2015 9:39 PM, 임정택 <ka...@gmail.com> wrote:
>
>
>  Parth,
> Thanks for information!
> Since there were some trials, my trial seems to be valid. :)
>
> Btw, I've seen succeed build from Travis CI, please see
> https://travis-ci.org/HeartSaVioR/storm/jobs/54211636
> Based on this we can see we already overcome multi-lang test, too.
>
> I've got another hurdle, we should open test-reports directory to see
> clojure tests, which I can't find clearer solution.
> We should rely on stdout / stderr, or upload these to somewhere.
>
> Please expose your any ideations about this.
>
> Regards.
> Jungtaek Lim (HeartSaVioR)
>
> 2015-03-26 9:51 GMT+09:00 Parth Brahmbhatt <pb...@hortonworks.com>:
>
> > IIRC, Taylor and Bobby both tried to setup CI and got stuck because of
> > multi-lang feature which needs ruby/node.js/python to be installed on the
> > host.
> >
> > Thanks
> > Parth
> >
> > On 3/25/15, 5:10 PM, "임정택" <ka...@gmail.com> wrote:
> >
> > >Hi all!
> > >
> > >I'd like to hear your opinion on adopting public CI.
> > >Now Apache Storm takes advantage of Github, we can apply Travis CI to
> some
> > >more advantages.
> > >Detailed informations are on JIRA issue (
> > >https://issues.apache.org/jira/browse/STORM-704).
> > >
> > >If you don't know Travis CI, it's better to take a look at.
> > >https://travis-ci.org/xetorthio/jedis
> > >
> > >Actually I'm trying to integrate it, and resolved many hurdles but got
> > >stuck.
> > >
> > >If you're interested in, please participate to resolve issue. :)
> > >
> > >Important question on this, I don't know why Storm didn't have CI.
> > >Is there some kind of decision about not having CI?
> > >If then this issue should be resolved as invalid.
> > >
> > >Thanks!
> > >
> > >Regards.
> > >Jungtaek Lim (HeartSaVioR)
> >
> >
>
>
> --
> Name : 임 정택
> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
> Twitter : http://twitter.com/heartsavior
> LinkedIn : http://www.linkedin.com/in/heartsavior
>
>
>



-- 
Name : 임 정택
Blog : http://www.heartsavior.net / http://dev.heartsavior.net
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior