[ https://issues.apache.org/jira/browse/CALCITE-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686284#comment-16686284 ]
ASF GitHub Bot commented on CALCITE-2412: ----------------------------------------- Github user F21 commented on the issue: https://github.com/apache/calcite-avatica/pull/65 Thanks @snuyanzin ! That looks great! When infra enables appveyor (they should post a reply in [INFRA-17249](https://issues.apache.org/jira/browse/INFRA-17249)), can you add the badge to the readme and squash again? Then just merge the PR as everything else looks good to me 👍 > Avatica/Calcite tests against Windows via Appveyor > -------------------------------------------------- > > Key: CALCITE-2412 > URL: https://issues.apache.org/jira/browse/CALCITE-2412 > Project: Calcite > Issue Type: Improvement > Components: build > Reporter: Sergey Nuyanzin > Assignee: Julian Hyde > Priority: Major > > Unfortunately Travis does not support Windows > https://github.com/travis-ci/travis-ci/issues/2104. There is a suggestion to > use Appveyor. > There are PRs attached both for Avatica and Calcite (i tried to make similar > to travis.yml) > The only different Java option for Calcite is {code}-Djna.nosys=true{code} > which is required to overcome > https://github.com/java-native-access/jna/issues/384 while Appveyor build. > Also unfortunately there is no option to have parallel build even between > projects (at least for free accounts) => to speed up the process I use only > java8 > + in case of Calcite do not use cache as Appveyor fails to save because of > the size - I guess it is also free account limitation > P.S. it should be noted that to have successful build on Appveyor > CALCITE-2409 should be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)