Good question. It can replace Jenkins, integrates automatically (only I think) with Github, and is orders of magnitude easier to use than Jenkins. A lot of other projects use it but I was surprised to hear Apache favored it. Doesn’t Apache have some draconian requirement to control all bits of the project pipeline and workflow?
In our case would it be able to replace Jenkins or is it extra work? BTW slightly off topic... the Slack thing is set up for Apache.org. It requires you to have an @apache.org email. That means other projects can create their own channel. It is also gratis and so will eventually be overwhelmed if lots of other projects start using it. On Apr 17, 2015, at 12:31 AM, Stevo Slavić <[email protected]> wrote: Before I cast my vote can somebody please explain which problem are we trying to or expect from this to be solved? Kind regards, Stevo Slavic. On Apr 17, 2015 9:22 AM, "Ted Dunning" <[email protected]> wrote: > Totally simple if the project has a standard build/test structure. > > For t-digest it took about 4 lines of yaml checked into the root > directory. The documentation on travis is excellent and the process of > setup is easy. > > > On Fri, Apr 17, 2015 at 3:27 AM, Andrew Musselman < > [email protected]> wrote: > >> Worth trying out though I've never used Travis; what work effort is >> required, any idea? >> >> On Thursday, April 16, 2015, Suneel Marthi <[email protected]> >> wrote: >> >>> Would this be an additional CI we would like to add to Mahout ? >>> >>> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci >>> >>> I am up for it. >>> >>> +1 >>> >> >
