Let's see what Travis replies to Robert, but in general I agree with Max.

Travis helped a lot to discover certain race conditions in the last weeks... I 
would like to not ditch it completely as Max suggested.

On 24 Mar 2015, at 16:03, Maximilian Michels <m...@apache.org> wrote:

> I would also like to continue using Travis but the current situation is not
> acceptable because we practically can't use Travis anymore for pull
> requests or the current master. If it cannot be resolved then I think we
> should move on.
> The builds service team [1] at Apache offers Jenkins [2] for continuous
> integration. I think it should be fairly simple to set up. We could still
> use Travis in our forked repositories but have a reliable CI solution for
> the master and pull requests.

Reply via email to