ci: run independent steps in parallel - #775
Draft
caugner wants to merge 1 commit into
Draft
Conversation
Contributor
|
b26bc95 was deployed to: https://rari-pr775.review.mdn.allizom.net/ |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Update CI workflows to run independent setup steps in parallel using the new GitHub Actions
background/wait-allstep keywords._build.yml: mark all seven repository checkouts asbackground: trueand add await-allbarrier beforeSetup Node(the first step depending on the content checkout)._test-content-run.yml: background the content/translated-content checkouts, the artifact download, and the translated-content env setup, thenwait-all;chmodof the binary runs after the barrier so it can't race the download.Motivation
Speed up CI by overlapping independent, network-bound checkout and download steps instead of running them serially.
Additional details
Uses the parallel step keywords introduced in GitHub Actions on 2026-06-25: https://github.blog/changelog/2026-06-25-actions-steps-can-now-be-run-in-parallel/
Related issues and pull requests