Hi Folks, As part of https://issues.apache.org/jira/browse/ARROW-3385, we are planning to perform a snapshot release of the Gandiva Jar on each commit to master. This would be a platform independent jar that contains the core gandiva library and its jni bridge packaged for Mac, Windows and *nix platforms.
The current plan is to deploy separate snapshot jars for each OS through entries in the Gandiva CI matrix and then have a combine step that pulls in each OS specific jar and builds a jar that has all the native libraries. This build/deploy would happen only for commits on master branch and not for PR requests Does the plan sound ok (or) please let us know if there is a better way to achieve the same. If it sounds ok, can someone please help with the following 1. It looks like we only do travis builds and not appveyor for master in arrow. Any reason for this? 2. Even if we did appveyor is there a way to sequence the builds. Like wait for appveyor to complete before kicking off travis? Since we would need the dll to be pre-built. 3. Someone would need to configure the credentials to use for the ossrh deployment. The credentials would need access to deploy to org.apache.arrow. Thanks ahead!
