Update version of helix.jobmonitor to 11.0.0-beta.26406.8

[mmitche]

Contains a fix for retries of test uploads

[azure-pipelines]

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.

[Copilot]

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.jobmonitor from 11.0.0-beta.26404.8 to 11.0.0-beta.26406.8 in the local tool manifest.

[tarekgh]

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

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

[Copilot]

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": [

[Copilot]

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 pins 11.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": [

[Copilot]

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 to 11.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 if 26406.8 is the intended target).

    "microsoft.dotnet.helix.jobmonitor": {
      "version": "11.0.0-beta.26411.1",
      "commands": [

[Copilot]

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": [

[Copilot]

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": [

[mmitche]

/azp run runtime

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

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

• enableHelixJobMonitor is defined twice with the same value. Since nothing between these entries redefines it, the second definition is redundant and makes it unclear which value is intended to be authoritative. Consider keeping a single definition with a comment that references the actual default being overridden.

  # 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 JobMonitor is being updated to 11.0.0-beta.26406.8, but the tool manifest pins microsoft.dotnet.helix.jobmonitor to 11.0.0-beta.31411.7. Please align the pinned version (or update the PR title/description if 31411.7 is the intended version).

    "microsoft.dotnet.helix.jobmonitor": {
      "version": "11.0.0-beta.31411.7",
      "commands": [

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.config/dotnet-tools.json:31

• The PR title says helix.jobmonitor is being updated to 11.0.0-beta.26406.8, but the tool manifest pins microsoft.dotnet.helix.jobmonitor to 11.0.0-beta.31411.8. Please align the PR description/title and the pinned version so reviewers know which build is intended (and so we can trace the source of the retry fix).

    "microsoft.dotnet.helix.jobmonitor": {
      "version": "11.0.0-beta.31411.8",
      "commands": [

[Copilot]

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:54

• enableHelixJobMonitor is defined twice with the same value. Since the later definition already forces the override after the variable templates, the earlier block is redundant and makes it harder to reason about which value is intended.

  - name: enableHelixJobMonitor
    value: true
  - template: /eng/pipelines/helix-platforms.yml

.config/dotnet-tools.json:31

• The PR metadata says this updates helix.jobmonitor to 11.0.0-beta.26406.8, but the manifest is being updated to 11.0.0-beta.31411.9. Please align the PR title/description and the tool version so reviewers can confirm the intended tool build (and that it contains the needed fix).

    "microsoft.dotnet.helix.jobmonitor": {
      "version": "11.0.0-beta.31411.9",
      "commands": [

[mmitche]

/azp run runtime

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[mmitche]

/azp run runtime

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[mmitche]

/azp run runtime

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (3)

eng/pipelines/runtime.yml:78

• testResultUploadParallelism: 48 is a significant deviation from the template default (8). Please add a brief rationale inline so future maintainers understand why this value is safe and necessary (and can tune it if AzDO/Helix throttles).

            testResultUploadParallelism: 48

eng/pipelines/runtime.yml:58

• enableHelixJobMonitor is already set to true earlier in this file (immediately after importing /eng/pipelines/common/variables.yml), and /eng/pipelines/helix-platforms.yml does not currently override it. This second definition is redundant and the comment is misleading, which makes the variables section harder to reason about.

This issue also appears on line 78 of the same file.

  # 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 says the Helix job monitor is being updated to 11.0.0-beta.26406.8, but the tool manifest pins microsoft.dotnet.helix.jobmonitor to 11.0.0-beta.31411.10 (and the previous value was 11.0.0-beta.26407.8). Please align the PR title/description with the actual version being consumed, or adjust the pinned version if the title is the intended target.

      "version": "11.0.0-beta.31411.10",

[Copilot]

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 pipeline variable enableHelixJobMonitor is currently set twice (first false, then immediately overridden to true). This makes the earlier assignment dead code and is easy to misread when troubleshooting pipeline behavior. Consider keeping a single definition that clearly documents the intended override source.

  # 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 this updates helix.jobmonitor to 11.0.0-beta.26406.8, but the pinned tool version here is 11.0.0-beta.31411.10. Please align the pinned version and the PR metadata (title/description) so it’s clear what’s actually being consumed by CI.

    "microsoft.dotnet.helix.jobmonitor": {
      "version": "11.0.0-beta.31411.10",
      "commands": [