-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CI: replace cancel-outdated-builds
with concurrency
group
#12477
Conversation
@bors r+ Thanks! There are no blockers on this from the Clippy side, so I don't think we have to wait for / bother Mark with this. |
CI: replace `cancel-outdated-builds` with `concurrency` group This is the last remaining [usage](https://github.com/search?q=org%3Arust-lang%20cancel-outdated-builds&type=code) of the [cancel-outdated-builds](https://github.com/rust-lang/simpleinfra/tree/master/github-actions/cancel-outdated-builds) CI action. Which means that if we remove its usage, we can remove the code of the action :) This action was replaced in `rust-lang/rust` with the native Github Actions `concurrency` group [last year](rust-lang/rust#112955). Note that unlike `rust-lang/rust`, which explicitly allows parallel try builds, `clippy` did not allow them, as all steps of the `clippy_bors.yaml` workflow used the `cancel-outdated-builds` action, regardless of the branch. So the new `concurrency` group mirrors that, which makes it a bit simpler than on `rust-lang/rust`. r? `@Mark-Simulacrum`
💔 Test failed - checks-action_test |
Added changelog (didn't know it's required). |
We need a changelog line, but if it is just an internal change, @bors retry |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
This is the last remaining usage of the cancel-outdated-builds CI action. Which means that if we remove its usage, we can remove the code of the action :)
This action was replaced in
rust-lang/rust
with the native Github Actionsconcurrency
group last year.Note that unlike
rust-lang/rust
, which explicitly allows parallel try builds,clippy
did not allow them, as all steps of theclippy_bors.yaml
workflow used thecancel-outdated-builds
action, regardless of the branch. So the newconcurrency
group mirrors that, which makes it a bit simpler than onrust-lang/rust
.changelog: none
r? @Mark-Simulacrum