ci: run independent workflow steps in parallel - #518
Open
caugner wants to merge 5 commits into
Open
Conversation
Run all repository checkouts in one `parallel` group, and run the search index and AI Help index updates alongside the bucket sync instead of before and after it. The checkout phase is bounded by the translated-content checkout (~32s) instead of the serial sum (~73s). Both index updates (~2 min each) only read the build output and hit Elasticsearch, OpenAI and Postgres, so they are fully hidden behind the ~15 min `gsutil` sync. The function deploy stays sequential because it re-authenticates `gcloud` with a different service account.
Same restructuring as in `prod-build.yml`: run all repository checkouts in one `parallel` group, and run the search index and AI Help index updates alongside the bucket sync instead of around it.
Run all repository checkouts (including the optional rari checkout) in one `parallel` group. The checkout phase is bounded by the translated-content checkout (~40s) instead of the serial sum (~90s). Unlike prod and stage, this workflow has no index updates to overlap with the bucket sync.
caugner
force-pushed
the
parallel-ci-steps
branch
from
September 10, 2026 09:38
9907499 to
5d4fa66
Compare
caugner
marked this pull request as ready for review
September 10, 2026 09:57
The step depends on the fred build output and the dex install, both of which are skipped when `SKIP_BUILD` is set, so it would fail in that case. Aligns it with the other steps in the same `parallel` group.
Running the step in a `parallel` group ahead of `Deploy Function` would otherwise let an OpenAI or Postgres failure block the function deploy, which previously ran before this step.
LeoMcA
requested changes
Sep 10, 2026
|
|
||
| - name: Update AI Help index with macros | ||
| if: ${{ ! vars.SKIP_BUILD }} | ||
| continue-on-error: true |
Member
There was a problem hiding this comment.
Hmm, I'm not so sure about this. Before, we had a nice situation where a failed ai help index would fail the build (alerting us), but not fail to update the content.
Now, do we either have to chose between us finding out, or us bringing down the content upload.
I think I'd move this back, it didn't really count in the "time from start to deploy" sense
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
3 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 the build workflows to run independent steps in
parallelgroups:prod-build.yml,stage-build.yml,test-build.yml: run all repository checkouts in one group.prod-build.yml,stage-build.yml: runUpdate search indexandUpdate AI Help index with macrosalongsideSync build. Both only read the build output.Motivation
Shorten the nightly builds by overlapping network-bound steps.
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/. A failing child fails the job at the end of the group, after all siblings have completed.
Expected savings, based on mean step durations of the last 5 (prod) / 3 (stage, test-build) successful runs:
Total: ~4.9 min (~12%) for prod, ~4.7 min (~11%) for stage, ~1 min (~2.5%) for test.
Not parallelized:
Deploy Functionvs.Sync build: both usegcloudwith different service accounts, so re-authenticating during a background sync would race on the credentials.review-deploy.yml:Setup gcloudalongsideSetup Node+npm ciwould save ~5s of ~100s.test.yml: measured no gain (~8s either way), since the checks are CPU-bound on the 2-core runner.actionlintdoesn't know theparallelkeyword yet and reports it as a syntax error.Related issues and pull requests
Part of mdn/fred#1862.