[
https://issues.apache.org/jira/browse/ARROW-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352711#comment-16352711
]
Jim Crist commented on ARROW-2083:
----------------------------------
I added something similar for dask to only build the hdfs tests on merge or if
the PR branch name contains `__TEST_HDFS__`. This is nice because that part of
the build matrix won't even be allocated, rather than starting the build and
immediately skipping it (which still takes a bit of time). The downside is it
has to switch on the branch name rather than a commit message string.
See https://github.com/dask/dask/blob/master/.travis.yml#L80.
> Support skipping builds
> -----------------------
>
> Key: ARROW-2083
> URL: https://issues.apache.org/jira/browse/ARROW-2083
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Uwe L. Korn
> Priority: Major
>
> While appveyor supports a [skip appveyor] you cannot skip only travis. What
> is the feeling about adding e.g.
> [https://github.com/travis-ci/travis-ci/issues/5032#issuecomment-273626567]
> to our build. We could also do some simple kind of change detection that we
> don't build the C++/Python parts and only Java and the integration tests if
> there was a change in the PR that only affects Java.
> I think it might be worthwhile to spend a bit on that to get a bit of load of
> the CI infrastructure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
