Add script to run Helix Job Monitor for Azure DevOps builds

[premun]

A quick tool that you give build URI and it runs the monitor locally

[Copilot]

Pull request overview

Adds a new PowerShell utility script to help developers run the Helix Job Monitor locally for a given Azure DevOps build results URL, resolving the relevant repo/stage metadata from the build timeline.

Changes:

• Introduces scripts/run-helix-job-monitor.ps1 to fetch build + timeline metadata from Azure DevOps and locate Helix Job Monitor jobs.
• Resolves the owning stage/stage attempt and constructs the Microsoft.DotNet.Helix.JobMonitor command-line arguments (with an -ArgsOnly output mode).
• Runs the Job Monitor via eng/common/dotnet.ps1 against the JobMonitor project.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

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

Suppressed comments (2)

scripts/run-helix-job-monitor.ps1:228

• eng/common/dotnet.ps1 is Windows-only (it invokes dotnet.exe with Windows path separators). As written, this script will fail when run under PowerShell on Linux/macOS. Use OS detection to select dotnet.ps1 vs dotnet.sh, and build paths with platform-neutral APIs instead of embedding ..\... in the child path.

$projectPath = Join-Path $PSScriptRoot '..\src\Microsoft.DotNet.Helix\JobMonitor\Microsoft.DotNet.Helix.JobMonitor.csproj'
$dotnetScript = Join-Path $PSScriptRoot '..\eng\common\dotnet.ps1'

scripts/run-helix-job-monitor.ps1:255

• When $dotnetScript resolves to eng/common/dotnet.sh (non-Windows), invoking it as & $dotnetScript ... may fail unless the file is executable. Calling it via bash is more reliable from PowerShell.

    & $dotnetScript run --project $projectPath --configuration Debug -- @jobMonitorArguments