-
Notifications
You must be signed in to change notification settings - Fork 303
Add blog post about moving Rust's CI to GitHub Actions #656
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
41 changes: 41 additions & 0 deletions
41
posts/inside-rust/2020-07-23-rust-ci-is-moving-to-github-actions.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
layout: post | ||
title: "Rust's CI is moving to GitHub Actions" | ||
author: Pietro Albini | ||
team: the infrastructure team <https://www.rust-lang.org/governance/teams/operations#infra> | ||
--- | ||
|
||
The Rust Infrastructure Team is happy to announce that, as part of the | ||
[evaluation we started last year][eval], most of Rust’s CI is moving to GitHub | ||
Actions! While we don’t expect the change to have any impact to our users, the | ||
switch will considerably improve the experience for compiler contributors. | ||
|
||
One of the major pain points for compiler contributors over the past few years | ||
has been waiting for PRs to be merged. We value having an always-green master | ||
branch, and to ensure that we test and merge just one PR at a time, with the | ||
pietroalbini marked this conversation as resolved.
Show resolved
Hide resolved
|
||
other approved ones [waiting in the queue][homu]. Our CI is extensive too, with | ||
57 machines building and testing the compiler across all the platforms we | ||
support. On our previous system, each of those builders takes between three to | ||
pietroalbini marked this conversation as resolved.
Show resolved
Hide resolved
|
||
four hours to finish. Combined with testing one PR at a time, this often causes | ||
PRs to wait in the queue for days before being tested. | ||
|
||
Making the CI setup faster is a permanent goal of the Infrastructure Team, and | ||
GitHub Actions provided us with a great opportunity to improve landing time: | ||
GitHub offered to sponsor a fully managed, private pool of 8-core VMs to run | ||
our builds on, which is a big improvement compared to the 2-core VMs we were | ||
previously using. GitHub Actions also provides most of the features we loved | ||
about Azure Pipelines while being integrated with GitHub’s permissions and UI, | ||
which made the switch even more fruitful. | ||
|
||
As of July 22nd, all the CI builds for the [rust-lang/rust] repository except | ||
for macOS builds are running exclusively on GitHub Actions! We’re still running | ||
macOS builds on Azure Pipelines for the time being, as we’re waiting on GitHub | ||
to fix [issue #71988][71988], but we hope to move them to GitHub Actions soon. | ||
|
||
We’d like to thank GitHub for sponsoring our CI builders and Microsoft for the | ||
Azure Pipelines capacity we used over the past year. | ||
|
||
[eval]: https://blog.rust-lang.org/inside-rust/2019/11/14/evaluating-github-actions.html | ||
[homu]: https://bors.rust-lang.org/queue/rust | ||
[rust-lang/rust]: https://github.com/rust-lang/rust | ||
[71988]: https://github.com/rust-lang/rust/issues/71988 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.