[
https://issues.apache.org/jira/browse/ARROW-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260004#comment-17260004
]
Jorge Leitão edited comment on ARROW-11140 at 1/6/21, 7:18 PM:
---------------------------------------------------------------
[~apitrou], thanks! [~kszucs] solved this in a smarter way within buildkite. I
was also able to address the caching / artifacts, which unblocks this.
I have pushed the latest version to github. [~kszucs], it assumes that there
are 3 queues:
* {{docker}}, any machine that can run a docker job using the docker plugin
(basically can run docker)
* {{macos}}, macos machine with rust installed
* {{windows}}, windows machine with rust installed
If / when we have the runners, the pipeline should reproduce the same jobs that
we have on github for Rust.
I do not have strong opinions here, I just used the same setup that we have on
github wrt to the runners. It looks as follows on my repo / account, where I
have one (macos) agent:
[https://buildkite.com/test-811/example/builds?branch=buildkite]
was (Author: jorgecarleitao):
[~apitrou], thanks! [~kszucs] solved this in a smarter way within buildkite. I
was also able to address the caching / artifacts, which unblocks this.
I have pushed the latest version to github. [~kszucs], it assumes the following:
There are 3 queues:
* {{docker}}, that can run a docker job using the docker plugin (basically can
run docker)
* {{macos}}, that is a macos machine with rust installed
* {{windows}}, that is a windows machine with rust installed
If / when we have the runners, the pipeline should reproduce the same jobs that
we have on github for Rust.
I do not have strong opinions here, I just used the same setup that we have on
github wrt to the runners. It looks as follows on my repo / account, where I
have one (macos) agent:
[https://buildkite.com/test-811/example/builds?branch=buildkite]
> [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: 50m
> 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)
