Skip to content

[net11.0] Use Helix job monitor for unit tests #37852

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kubaflo merged 3 commits into from
Aug 26, 2026
+62 −3
Merged

[net11.0] Use Helix job monitor for unit tests #37852

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e9efd01
[net11.0] Use Helix job monitor for unit tests
kubaflo Aug 26, 2026
d1ca149
[net11.0] Isolate Helix job monitor setup
kubaflo Aug 26, 2026
b03c30e
[net11.0] Couple Helix monitor timeouts
kubaflo Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .config/dotnet-tools.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,13 @@
],
"rollForward": false
},
"microsoft.dotnet.helix.jobmonitor": {
"version": "11.0.0-beta.26379.102",
"commands": [
"dotnet-helix-job-monitor"
],
"rollForward": false
},
"api-tools": {
"version": "1.3.5",
"commands": [
Expand Down
12 changes: 9 additions & 3 deletions eng/pipelines/arcade/stage-helix-tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,9 +91,15 @@ stages:
DOTNET_TOKEN: $(dotnetbuilds-internal-container-read-token)
PRIVATE_BUILD: $(PrivateBuild)

- script: $(_msbuildCommand) "${{ parameters.helixProject }}" -warnAsError 0 -restore /p:Configuration=${{ BuildConfiguration }} /p:HelixInternal="${{ parameters.helixInternal }}" /p:TestRunNameSuffix="_${{ BuildConfiguration }}" /p:SkipInitInternalTooling=true /bl:$(Build.Arcade.LogsPath)${{ BuildConfiguration }}/helix_tests.binlog ${{ parameters.extraHelixArguments }}
- script: $(_msbuildCommand) "${{ parameters.helixProject }}" -warnAsError 0 -restore /p:Configuration=${{ BuildConfiguration }} /p:EnableHelixJobMonitor=true /p:HelixInternal="${{ parameters.helixInternal }}" /p:TestRunNameSuffix="_${{ BuildConfiguration }}" /p:SkipInitInternalTooling=true /bl:$(Build.Arcade.LogsPath)${{ BuildConfiguration }}/helix_tests.binlog ${{ parameters.extraHelixArguments }}
displayName: Run Helix Tests
env:
SYSTEM_ACCESSTOKEN: $(System.AccessToken) # We need to set this env var to publish helix results to Azure Dev Ops
SYSTEM_ACCESSTOKEN: $(System.AccessToken)
HelixAccessToken: ${{ parameters.HelixAccessToken }}


- template: /eng/common/core-templates/job/helix-job-monitor.yml
parameters:
timeoutInMinutes: 360
organization: dotnet
repository: maui
helixAccessToken: ${{ parameters.HelixAccessToken }}

@kubaflo kubaflo Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The monitor intentionally starts alongside the submitter jobs. The pinned runner polls the same-stage Azure DevOps timeline and does not terminate until AreNonMonitorJobsComplete is true; while the submitters are running, a first poll with zero Helix jobs therefore continues polling and discovers their durable Helix records after submission. This is also the canonical Arcade template behavior (dependsOn defaults to an empty list), and the monitor design explicitly describes observing timeline jobs running alongside it. Adding dependsOn is not required here.

Loading