[
https://issues.apache.org/jira/browse/ARROW-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Leitão updated ARROW-11140:
---------------------------------
Description:
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)
was:
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.
Goals:
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)
> [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, Rust
> Reporter: Jorge Leitão
> Assignee: Jorge Leitão
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 20m
> 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)