[
https://issues.apache.org/jira/browse/ARROW-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17661053#comment-17661053
]
Rok Mihevc commented on ARROW-4030:
-----------------------------------
This issue has been migrated to [issue
#20631|https://github.com/apache/arrow/issues/20631] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [CI] Use travis_terminate to halt builds when a step fails
> ----------------------------------------------------------
>
> Key: ARROW-4030
> URL: https://issues.apache.org/jira/browse/ARROW-4030
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Continuous Integration
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I noticed that Travis CI will soldier onward if a step in its {{script:}}
> block fails. This wastes build time when there is an error somewhere early on
> in the testing process
> For example, in the main C++ build, if {{travis_script_cpp.sh}} fails, then
> the subsequent steps will continue.
> It seems the way to deal with this is to add {{|| travis_terminate 1}} to
> lines that can fail
> see
> https://medium.com/@manjula.cse/how-to-stop-the-execution-of-travis-pipeline-if-script-exits-with-an-error-f0e5a43206bf
> I also found this discussion
> https://github.com/travis-ci/travis-ci/issues/1066
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
