-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Rust] [CI] Try out buildkite #18444
Comments
Jorge Leitão / @jorgecarleitao:
with the default github integration? |
Jorge Leitão / @jorgecarleitao: |
Jorge Leitão / @jorgecarleitao: can't make cache working. can't make artifacts working. |
Antoine Pitrou / @pitrou: |
Jorge Leitão / @jorgecarleitao: I have pushed the latest version to github. @kszucs, it assumes that there are 3 queues:
|
Jorge Leitão / @jorgecarleitao: |
Andrew Lamb / @alamb: |
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)
Reporter: Jorge Leitão / @jorgecarleitao
PRs and other links:
Note: This issue was originally created as ARROW-11140. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: