Repository navigation
Use YAML to control pipeline triggers - #388
Merged
Vladimir Morozov (vmoroz) merged 1 commit intoOct 17, 2026
Merged
Conversation
There was a problem hiding this comment.
🔵 Needs a closer look
Human verification is needed that Azure DevOps trigger overrides are removed and scheduled CI runs should trigger downstream releases.
No open issues 🎉
What changed in this PR
Moves pipeline trigger configuration into YAML for main-branch validation, CI, and downstream releases.
Changes:
- Enables PR validation targeting
mainand batched CI formain. - Adds monthly keep-alive schedules to PR and CI pipelines.
- Triggers releases after successful CI completion on
main.
| File | Description |
|---|---|
.ado/release-pipeline.yml |
Enables the main-branch CI completion trigger. |
.ado/pr-pipeline.yml |
Adds PR validation and monthly scheduling. |
.ado/ci-pipeline.yml |
Adds batched CI and monthly scheduling. |
Review effort: Balanced
Danny van Velzen (dannyvv)
approved these changes
Oct 16, 2026
Benchmark ResultsTotal benchmarks: 204 Inputs: baseline/baseline.json, bench_result.json v8 (6176ms, 6249ms) +1.2%
test-suites (317886ms, 317629ms) -0.1%
micros (60876ms, 60878ms) +0.0%
jit-benches (8563ms, 6212ms) -27.5%
many-subclasses (73437ms, 76056ms) +3.6%
map-objects (3627ms, 3614ms) -0.4%
map-strings (4335ms, 4305ms) -0.7%
nbody (3448ms, 2909ms) -15.6%
string-switch (6503ms, 6031ms) -7.3%
raytracer (5608ms, 5484ms) -2.2%
MiniReact (30332ms, 29476ms) -2.8%
widgets (12934ms, 12638ms) -2.3%
|
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
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
Make pipeline triggers and keep-alive schedules reviewable in YAML instead of
the pipeline UI.
main, not the deprecatedrnw/*branches.inactive. Scheduled CI still starts a release and publishes its date-based
version.
mainthrough aYAML pipeline-resource trigger.
Test Plan
All three entry files pass Azure Pipelines preview, with their expanded triggers
and schedules checked.
Microsoft Reviewers: Open in CodeFlow