Update Helix Job Monitor and turn it on for the runtime pipeline - #131969
Merged
Merged
Conversation
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the pinned .NET local tool version for microsoft.dotnet.helix.jobmonitor to a newer 11.0.0-beta build, so the repo’s dotnet tool restore / Helix job monitor usage picks up the intended fix.
Changes:
- Bump
microsoft.dotnet.helix.jobmonitorfrom11.0.0-beta.26404.8to11.0.0-beta.26406.8in the local tool manifest.
Member
|
Hopefully this will fix the job stuck here https://dev.azure.com/dnceng-public/public/_build/results?buildId=1543009&view=logs&s=6884a131-87da-5381-61f3-d7acc3b91d76&j=078edc60-2a90-5618-e72d-426a045b11f0 |
Contributor
|
Tagging subscribers to this area: @dotnet/area-meta |
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.config/dotnet-tools.json:31
- The Helix Job Monitor version bump is only applied to the local tool manifest here, but the repo still pins Microsoft.DotNet.Helix.JobMonitor to 11.0.0-beta.26404.8 in eng/Version.Details.xml and eng/Version.Details.props (similar tools like XHarness are kept in sync). This leaves two different "source of truth" versions in the repo and can cause confusion / dependency-flow churn; please update the Arcade dependency pins as well (or explain why this tool is intentionally diverging from Version.Details).
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.26406.8",
"commands": [
mmitche
commented
Aug 7, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.config/dotnet-tools.json:31
- The PR title indicates updating helix.jobmonitor to
11.0.0-beta.26406.8, but the tool manifest pins11.0.0-beta.26407.3. Please align the pinned version with the intended update (or update the PR title/description to match) to avoid confusion when tracking tool rollouts.
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.26407.3",
"commands": [
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.config/dotnet-tools.json:31
- The PR title says the helix.jobmonitor version is being updated to
11.0.0-beta.26406.8, but the tool manifest is actually updated to11.0.0-beta.26411.1. Please align these (either update the PR title/description to match the version being shipped, or change the version here if26406.8is the intended target).
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.26411.1",
"commands": [
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.config/dotnet-tools.json:31
- The PR title says the helix.jobmonitor version is being updated to 11.0.0-beta.26406.8, but this change pins microsoft.dotnet.helix.jobmonitor to 11.0.0-beta.26411.1. Please align the PR title/description with the version actually being used, or update the manifest to the intended version.
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.26411.1",
"commands": [
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.config/dotnet-tools.json:31
- PR title says update helix.jobmonitor to 11.0.0-beta.26406.8, but the actual change sets it to 11.0.0-beta.26411.1 (from 26407.8). Please align the PR title/description with the version being introduced, or adjust the version here to match the stated target.
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.26411.1",
"commands": [
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (2)
.config/dotnet-tools.json:30
- The PR title says the Helix job monitor is being updated to 11.0.0-beta.26406.8, but the tool manifest is updated to 11.0.0-beta.31411.1. Please align the PR metadata and the actual version being consumed (either update the title/description or change the manifest version) so it’s clear what build is being taken and why.
"version": "11.0.0-beta.31411.1",
NuGet.config:15
- Adding the new 'general-testing' package source affects restores for the entire repo (extra feed to probe and a potentially different source of packages). If this feed is only needed to acquire the updated helix.jobmonitor tool, consider scoping it to just that restore path (or document why the global source addition is required) to avoid unintended restore/source selection changes.
<add key="general-testing" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/general-testing/nuget/v3/index.json" />
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.config/dotnet-tools.json:31
- The PR title/description says the update is to helix.jobmonitor 11.0.0-beta.26406.8, but the change here updates to 11.0.0-beta.31411.2 (from 11.0.0-beta.26407.8). Please confirm which version is intended and align either this value or the PR metadata so the change is traceable.
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.31411.2",
"commands": [
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 4 changed files in this pull request and generated no new comments.
Suppressed comments (2)
eng/pipelines/runtime.yml:58
enableHelixJobMonitoris assigned twice with conflicting values (false then true). Since there are no uses between these assignments, the first assignment is redundant and makes it harder to understand which behavior is intended.
# Keep the monitor enabled in the PR merge even when the target branch
# temporarily changes the default above.
- name: enableHelixJobMonitor
value: true
.config/dotnet-tools.json:30
- The PR title/description says the helix job monitor is being updated to
11.0.0-beta.26406.8, but this change pinsmicrosoft.dotnet.helix.jobmonitorto11.0.0-beta.31411.16. Please reconcile the intended version (or update the PR title/description to match what is actually being used).
"version": "11.0.0-beta.31411.16",
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 4 changed files in this pull request and generated no new comments.
Suppressed comments (2)
eng/pipelines/runtime.yml:58
- The variable
enableHelixJobMonitoris declared twice (firstfalse, thentrue). In Azure Pipelines the later value wins, which makes the earlier entry misleading and easy to accidentally “toggle” without effect. Consider keeping a single declaration with the intended value and keephelix-platforms.ymlas a separate entry.
- name: enableHelixJobMonitor
value: false
- template: /eng/pipelines/helix-platforms.yml
# Keep the monitor enabled in the PR merge even when the target branch
# temporarily changes the default above.
- name: enableHelixJobMonitor
value: true
.config/dotnet-tools.json:31
- The PR title says the job monitor is being updated to
11.0.0-beta.26406.8, but the manifest pinsmicrosoft.dotnet.helix.jobmonitorto11.0.0-beta.31411.17. Please align the pinned version (and any related feed changes) with the intended version, or update the PR title/description accordingly.
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.31411.17",
"commands": [
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.
Suppressed comments (1)
Previously missed (1) — in code that hasn't changed since the last review.
eng/pipelines/runtime.yml:58
enableHelixJobMonitoris defined twice in the same variables block. The second definition currently overrides the first, making the initialfalseassignment redundant and potentially confusing (and order-dependent for template evaluation). Prefer a single definition with the effective value.
# Keep the monitor enabled in the PR merge even when the target branch
# temporarily changes the default above.
- name: enableHelixJobMonitor
value: true
Use the promoted scalable Job Monitor, add configurable result-upload parallelism, and enable the monitor in the runtime pipeline. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: f6ec29d9-df3d-405a-a823-571c6a18e447
mmitche
force-pushed
the
mmitche-patch-1
branch
from
August 24, 2026 21:00
6a4a54e to
dd396ca
Compare
premun
approved these changes
Aug 24, 2026
premun
approved these changes
Aug 25, 2026
runtime pipeline
akoeplinger
added a commit
that referenced
this pull request
Sep 21, 2026
## Description Backport the Helix job monitor integration from main/release/11.0, including the groundwork from #129690 and #132150 and the re-enablement in #131969. Includes the subsequent fixes for empty stages (#132019), conditional monitor inclusion (#132882, #132884), parameter forwarding (#133002), performance monitoring (#132807, #133480), and internal credentials (#133633, #133688, #133885). - Use `Microsoft.DotNet.Helix.JobMonitor` version `10.0.0-beta.26461.103`, matching release/10.0's existing Arcade/VMR build. - Preserve the existing SDK, shared Arcade templates, queues, and release/10.0 job layouts. - Follow upstream enablement, except scheduled libraries outerloop runs retain release/10.0's existing warning-only reporting policy. - Leave SuperPMI's post-Helix processing unchanged. The separate perf-slow enablement in #133726 is not included. ## Customer Impact CI infrastructure only; no shipped runtime changes. Moves Helix waiting and test-result reporting into the standalone monitor for the enabled pipelines. ## Regression Not a product regression fix; backports existing CI infrastructure and its follow-up fixes. ## Testing - Validated YAML/JSON/XML configuration and preservation of unrelated settings. - Checked 43 entry pipelines, 149 forwarding sites, and 516 public/internal, PR/scheduled/manual, and normal/staging combinations, plus disabled-mode behavior. - Exercised MSBuild child-property forwarding and the pinned SDK's waiting/reporter properties, including environment-based opt-in. - Restored the monitor and verified its CLI compatibility under .NET 10. No product build or live Azure DevOps pipeline execution was performed locally. ## Risk Changes CI scheduling and result reporting, not product behavior. Uses the monitor package matching the branch's existing toolset and retains the release/10.0-specific scheduled outerloop failure policy. End-to-end Azure DevOps validation is still required. > [!NOTE] > This PR description and backport were prepared with GitHub Copilot. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: aae9b201-32a8-45eb-ae1a-db80a0ab4156
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Microsoft.DotNet.Helix.JobMonitorto11.0.0-beta.26424.2from Arcade build20260824.248