RE: Travis-ci & geode-native repo

2019-08-26 Thread Alberto Bustamante Reyes
that was fast: I contacted Travis support and they increased the timeout for us 🙂 De: Alberto Bustamante Reyes Enviado: lunes, 26 de agosto de 2019 13:03 Para: dev@geode.apache.org Asunto: RE: Travis-ci & geode-native repo Thanks for the answer Jake (sorry

RE: Travis-ci & geode-native repo

2019-08-26 Thread Alberto Bustamante Reyes
: miércoles, 7 de agosto de 2019 17:11 Para: dev@geode.apache.org 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 ei

Re: Travis-ci & geode-native repo

2019-08-07 Thread Jacob Barrett
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 pipelin

Travis-ci & geode-native repo

2019-08-07 Thread 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