[
https://issues.apache.org/jira/browse/ARROW-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371533#comment-16371533
]
Wes McKinney commented on ARROW-2192:
-------------------------------------
I think the Appveyor builds are OK as is (they will always run), but we can
address them further in the future if need be
> Commits to master should run all builds in CI matrix
> ----------------------------------------------------
>
> Key: ARROW-2192
> URL: https://issues.apache.org/jira/browse/ARROW-2192
> Project: Apache Arrow
> Issue Type: Bug
> Components: Continuous Integration
> Reporter: Wes McKinney
> Assignee: Antoine Pitrou
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.9.0
>
>
> After ARROW-2083, we are only running builds related to changed components
> with each patch in Travis CI and Appveyor.
> The problem with this is that when we merge patches to master, our Travis CI
> configuration (implemented by ASF infra to help alleviate clogged up build
> queues) is set up to cancel in-progress builds whenever a new commit is
> merged.
> So basically we could have in our timeline:
> * Patch merged affecting C++, Python
> * Patch merged affecting Java
> * Patch merged affecting JS
> So when the Java patch is merged, any in-progress C++/Python builds will be
> cancelled. And if the JS patch comes in, the Java builds would be immediately
> cancelled.
> In light of this I believe on master branch we should always run all of the
> builds unconditionally
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
