Hi Pono, Thank you for bringing that to my information. Ultimately, we want to be able to run tests for Github pull requests, similar to kafka: https://github.com/apache/kafka/pull/2012.
I understand that Calcite already has Jenkins setup. What would be required to set up the ASFBot to build PRs on Github? Unfortunately, I wasn't able to find much information regarding that on the ASFBot page here: https://www.apache.org/dev/asfbot.html Thanks again, Francis -----Original Message----- From: Pono Takamori [mailto:[email protected]] Sent: Wednesday, 12 October 2016 10:18 AM To: [email protected] Cc: [email protected] Infrastructure <[email protected]>; [email protected] Subject: Re: Setting up Wercker continuous integration for Calcite Wercker has the same problem a lot of Github integration services do, in that it needs write access to the repo in order to edit hooks, etc. This is a non-starter for us as we cannot allow write access to ASF repos from third parties. The test you mention of maintaining a fork and running against that is the best we can allow currently. -Pono on behalf of Infra On Tue, Oct 11, 2016 at 10:37 PM, <[email protected]> wrote: > Hello, > > > > We have discovered that Travis has some resource limitations that > prevents tests for Calcite to run in a reliable manner. We have tested > Wercker on a fork and it is much more reliable and stable. > > > > We would like to request the infrastructure team make the following > changes to the Calcite Github repo: > > > > 1. Disable Travis continuous integration in the repository settings. > > 2. Enable Wercker for the repository by logging into wercker.com and > creating a new app as per the attached image. > > > > Thank you very much, > > Francis > >
