actually our biggest enemy with travis is time - there used to be a time limit for builds (60 minutes??) - if that's still there integration tests likely won't finish in that period and will fail.
On Fri, Nov 20, 2015 at 12:43 PM, Stephen Mallette <[email protected]> wrote: > I've lost touch with the features of Travis. If it can be configured to > run our integration tests (maybe just on successful "mvn clean install" > jobs?) then i'm good with using it as our CI tool. > > On Fri, Nov 20, 2015 at 12:00 PM, Dylan Millikin <[email protected] > > wrote: > >> Hey guys, >> >> I just made a very basic PR for travis, you can check this here : >> https://github.com/apache/incubator-tinkerpop/pull/148 >> >> The first thought behind this PR was to at least run "mvn clean install" >> on >> all PRs. This should be covered at the moment, but before we go any >> further >> with this it would be nice to get a discussion going around the various >> options. >> >> Are there any reasons why we would rather choose Jenkins over Travis? >> etc.. >> Also any ideas are more than welcome. >> >> Cheers. >> > >
