<div dir="ltr">Hello, <div><br></div><div>in APM we have changed travis image from 'STANDARD' to 'TRUSTY BETA' [1]. </div><div>So far it works great without any failed builds, before builds were failing all the time. </div><div>Even the build time has improved see [3] for master and [4] for PRs.</div><div>PR changing to 'TRUSTY BETA' [2].</div><div><br></div><div><br></div><div>[1]: <a href="https://docs.travis-ci.com/user/ci-environment/">https://docs.travis-ci.com/user/ci-environment/</a></div><div>[2]: <a href="https://github.com/hawkular/hawkular-apm/pull/494">https://github.com/hawkular/hawkular-apm/pull/494</a></div><div>[3]: <a href="https://travis-ci.org/hawkular/hawkular-apm/builds">https://travis-ci.org/hawkular/hawkular-apm/builds</a></div><div>[4]: <a href="https://travis-ci.org/hawkular/hawkular-apm/pull_requests">https://travis-ci.org/hawkular/hawkular-apm/pull_requests</a></div><div><br></div><div>Pavol</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 11, 2016 at 9:52 AM, Michael Burman <span dir="ltr"><<a href="mailto:miburman@redhat.com" target="_blank">miburman@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I'm proposing we get rid of the Travis for now (at least for metrics)<br>
and stick to something else, such as the old Jenkins. At the moment, it<br>
can take several runs for metrics PRs to finish, since Cassandra stops<br>
responding in the Travis runs every time. Yesterday I started my PR 4<br>
times, last week one PR for 10 times.<br>
<br>
22:28:24,629 ERROR [com.datastax.driver.core.<wbr>ControlConnection]<br>
(cluster1-reconnection-1) [Control connection] Cannot connect to any<br>
host, scheduling retry in 600000 milliseconds<br>
<br>
Sometimes it doesn't even get this far and fails with running the<br>
installation script of Cassandra. These errors have made the Travis runs<br>
completely irrelevant, whenever they fail it just makes sense to restart<br>
them without reading logs (we should get automatic script to restart<br>
always when it fails) until they succeed. No errors reported by Travis<br>
are trustworthy.<br>
<br>
We need a working CI solution and this isn't it. There's no "community<br>
visibility" if the results have no meaning, using Jenkins at least<br>
provides us with "failed / not failed", Travis doesn't provide even this.<br>
<br>
- Micke<br>
<br>
______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/hawkular-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font color="#999999">Pavol Loffay<br>Cell: +421948286055</font></div><div dir="ltr"><font color="#999999">Red Hat<br>Purkyňova 111 </font><span style="color:rgb(153,153,153);font-size:12.8px">TPB-B</span><font color="#999999"><br>612 45 Brno</font></div></div></div></div>
</div>