You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Andrew Lamb (Jira)" <ji...@apache.org> on 2021/04/26 12:46:02 UTC

[jira] [Closed] (ARROW-11140) [Rust] [CI] Try out buildkite

     [ https://issues.apache.org/jira/browse/ARROW-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Lamb closed ARROW-11140.
-------------------------------
    Resolution: Invalid

> [Rust] [CI] Try out buildkite
> -----------------------------
>
>                 Key: ARROW-11140
>                 URL: https://issues.apache.org/jira/browse/ARROW-11140
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: CI, Continuous Integration, Rust
>            Reporter: Jorge Leitão
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> Let's make a test to validate whether we can use buildkite on our own flows, which adds a lot of options in architectures and environments that we can test stuff on.
> Goal: validate that we can use buildkite on the rust builds.
> Requirements:
>  # pipeline starts when a PR is made
>  # result is sent back to github and users can access its logs
>  # we can use caches (e.g. [https://github.com/danthorpe/cache-buildkite-plugin] )
>  # we can actually run the builds
>  # we can limit the builds to only be triggered when certain parts of the repo change (i.e. not run when only C++ code changed)
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)