geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alberto Bustamante Reyes <>
Subject RE: Travis-ci & geode-native repo
Date Mon, 26 Aug 2019 11:03:10 GMT
Thanks for the answer Jake (sorry for the late answer, I was on holidays).

Do you know if Travis is offering that support from free?

The task of moving from Travis to Concourse sounds interesting, is there an existing ticket
about it?
De: Jacob Barrett <>
Enviado: miércoles, 7 de agosto de 2019 17:11
Para: <>
Asunto: Re: Travis-ci & geode-native repo

We worked with Travis support to increase our timeout on the backend. As you can see from
the Travis report it takes a long time to build. It doesn’t run any of the integration tests
either. We use it as a litmus test on PRs mostly.

There is a future goal to role the build into the same pipeline as the java sources and do
binary releases. If you would like to pick up that task it would allow you to run a full CI
of your own too.


> On Aug 7, 2019, at 7:42 AM, Alberto Bustamante Reyes <>
> Hi,
> I have a question about the CI of the Geode C++ client. I would like to set up Travis
on a fork of the geode-native repo. I thought that the only requirements to do so was to grant
permissions to the repo, but our travis tasks are failing due to the execution timeout is
50 minutes.
> I dont see in the travis.yaml any configuration about timeouts and I cannot find any
option to change that in Travis page. Could it be that geode-native repo is not using the
free version of Travis so it has a longer timeout? I have seen that tasks takes aprox 1 hour
and a half.
> Thanks!
> Alberto B.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message