vdiravka commented on issue #1493: DRILL-6777: Setup CircleCI configs for Drill URL: https://github.com/apache/drill/pull/1493#issuecomment-428915471 @ilooner Thanks for review. 1. I have created [INFRA-17133](https://issues.apache.org/jira/browse/INFRA-17133) ticket, but then I've noticed that INFRA can't allow write access for 3d party ([Apache Arrow + CircleCI](https://issues.apache.org/jira/browse/INFRA-15964?focusedCommentId=16351422&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16351422)). So here are two ways: * merge it and CircleCI builds will work for Drill forks only. * try to help INFRA to solve this issue via configuring CircleCI webhooks [[link](https://issues.apache.org/jira/browse/INFRA-12197?focusedCommentId=15652850&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15652850)] I think we can try the second way, but even just to merge .circleci to the Drill will be useful for the forks of committers and contributors, like in the Apache Cassandra [[link](https://github.com/apache/cassandra/tree/trunk/.circleci)]. I will post this question to our community to decide. 2. The status badge for README.md could be added once CirlceCI will be enabled for Drill. https://issues.apache.org/jira/browse/DRILL-6789 3. The ticket for caching already exists [DRILL-6780](https://issues.apache.org/jira/browse/DRILL-6780). There are also other future enhancements in [DRILL-6741](https://issues.apache.org/jira/browse/DRILL-6741), but even without them current Circle build runs faster with more tests than in Travis build.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
