You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Krisztian Szucs (JIRA)" <ji...@apache.org> on 2019/06/21 09:27:00 UTC
[jira] [Resolved] (ARROW-5664) Execute nightly crossbow tests on
CircleCI instead of Travis
[ https://issues.apache.org/jira/browse/ARROW-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Krisztian Szucs resolved ARROW-5664.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.14.0
Issue resolved by pull request 4631
[https://github.com/apache/arrow/pull/4631]
> Execute nightly crossbow tests on CircleCI instead of Travis
> ------------------------------------------------------------
>
> Key: ARROW-5664
> URL: https://issues.apache.org/jira/browse/ARROW-5664
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Packaging
> Reporter: Krisztian Szucs
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The spark integration test has hit the 50mins maximum build time on travis, whereas Circle can run jobs up to 5 hours. All of the nightly tests are run within docker containers so porting travis template to a circleci equivalent template should not be too hard. In order to properly report badges via @ursabot crossbow command, we also need to store which CI service executes a task. So the following changes are required:
> - Port https://github.com/apache/arrow/blob/master/dev/tasks/docker-tests/travis.linux.yml to a CircleCI equivalent
> - Store which CI is responsible for running a particular task https://github.com/apache/arrow/blob/master/dev/tasks/crossbow.py#L468
> - Update ursabot to generate badges based on the property added in the previous step
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)