Add run-nightly-stress.yml: dispatch nightly-stress-test.yml per branch - #70103
Open
charzl wants to merge 1 commit into
Open
Add run-nightly-stress.yml: dispatch nightly-stress-test.yml per branch#70103charzl wants to merge 1 commit into
charzl wants to merge 1 commit into
Conversation
Structured directly after run-nightly.yml (which does the same thing for nightly.yml): a workflow-requirements gate (RUN_SCHEDULED_BUILDS / fork / private-repo checks), then a matrix job that dispatches the target workflow on each branch with --ref matrix.branch, using a GitHub App token (actions/create-github-app-token) rather than the default GITHUB_TOKEN. master isn't in the matrix -- its own nightly-stress-test.yml already carries a `schedule:` trigger that GitHub actually honors (it's the default branch), so it doesn't need to be dispatched. This job exists for branches whose own `schedule:` is inert per GitHub's schedule-only-fires-on-default-branch behavior. 3006.x is the only branch in the matrix for now -- it's the only one with its own complete nightly-stress-test.yml (schedule + full workflow_dispatch inputs + job body all in one file, not split into a separate run-stress-test.yml). 3007.x/3008.x aren't listed; add them once each has its own copy of the file. Reuses the SKIP_NIGHTLY_STRESS_TEST opt-out var that nightly-stress-test.yml's own master-branch run already checks, so one variable controls both master's direct run and this dispatch.
2 tasks
charzl
added a commit
that referenced
this pull request
Aug 21, 2026
The previous wording described a rename to run-stress-test.yml and a new dispatcher file -- that belongs to PR #70103, not this PR. This PR only modifies nightly-stress-test.yml in place. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Part of VCOPS-100029 (multi-branch nightly stress test coverage).
schedule:triggers only ever fire off the repository's default branch, somaster's ownnightly-stress-test.ymlalready runs nightly, but3006.x's copy of the same file (companion PR #70099 -- a single self-contained file with its ownschedule:+ fullworkflow_dispatchinputs, not split into a separate dispatcher/executor pair) never actually fires on its own.This adds
run-nightly-stress.yml, structured directly after the existingrun-nightly.yml(which does the same job fornightly.ymlacross3006.x/3007.x/3008.x/master):workflow-requirementsgate: sameRUN_SCHEDULED_BUILDS/ fork / private-repo checks asrun-nightly.yml.trigger-branch-nightly-stress-buildsjob withstrategy: matrix: branch: [3006.x], dispatchinggh workflow run nightly-stress-test.yml --ref <branch>for each -- using a GitHub App token (actions/create-github-app-token), same asrun-nightly.yml, rather than the defaultGITHUB_TOKEN.masteris not in the matrix -- its ownnightly-stress-test.ymlalready fires directly via its ownschedule:(it's the default branch), so dispatching it here would be redundant.3007.x/3008.xaren't listed either -- neither has its own completenightly-stress-test.ymlyet; add them to the matrix once each does (no other changes needed, per #70099's file being kept default-free and branch-name-free for exactly this kind of straight port).Reuses
SKIP_NIGHTLY_STRESS_TEST, the same opt-out variablenightly-stress-test.yml's own master-branch run already checks, so one variable controls both master's direct run and this dispatch to other branches.Test plan
workflow-requirementsgate present, matrix branch list correct, dispatch step referencesnightly-stress-test.yml.0 2 * * *cron dispatchesnightly-stress-test.ymlon3006.xand that it runs successfully there.