[Hawkular-dev] Get rid of Travis?

[Lucas Ponce]

I am not a fun of travis.

I admit that sometimes it has weird behaviour, specially when you suspect your machine comes from an hibernate state and it needs a "warm up", so a first round fails but a second and next works good.

But I think that get rid of Travis perhaps is too aggressive.

Is there a possibility to study if we can "upgrade" and have a travis subscription/plan that gives us more resources ?

Other projects as ManageIQ uses travis in big setups and perhaps we can follow/adopt some of their practices.

One thing I miss from travis is that the machines are small to automate some performance/clustering tests for alerting, and those ones need to be executed locally.

But for integration tests it works "reasonable" in the sense that after "warm up" (first round) executions are stable and consistency.

Just my 2 cents.

----- Mensaje original -----
> De: "Michael Burman" <miburman at redhat.com>
> Para: hawkular-dev at lists.jboss.org
> Enviados: Martes, 11 de Octubre 2016 9:52:24
> Asunto: [Hawkular-dev] Get rid of Travis?
> 
> Hi,
> 
> I'm proposing we get rid of the Travis for now (at least for metrics)
> and stick to something else, such as the old Jenkins. At the moment, it
> can take several runs for metrics PRs to finish, since Cassandra stops
> responding in the Travis runs every time. Yesterday I started my PR 4
> times, last week one PR for 10 times.
> 
> 22:28:24,629 ERROR [com.datastax.driver.core.ControlConnection]
> (cluster1-reconnection-1) [Control connection] Cannot connect to any
> host, scheduling retry in 600000 milliseconds
> 
> Sometimes it doesn't even get this far and fails with running the
> installation script of Cassandra. These errors have made the Travis runs
> completely irrelevant, whenever they fail it just makes sense to restart
> them without reading logs (we should get automatic script to restart
> always when it fails) until they succeed. No errors reported by Travis
> are trustworthy.
> 
> We need a working CI solution and this isn't it. There's no "community
> visibility" if the results have no meaning, using Jenkins at least
> provides us with "failed / not failed", Travis doesn't provide even this.
> 
>    -  Micke
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>