[Azure Pipelines] Implement Copilot build detection with x64-linux first execution #45946

Copilot · 2025-06-11T20:49:09Z

Problem

Copilot-triggered workflows were overloading the Azure Pipelines pool by running all triplets in parallel, causing resource contention and slower feedback for both Copilot and regular users.

Solution

This PR implements automatic Copilot build detection and conditional execution logic:

🔍 Copilot Detection

Detects Copilot builds via multiple indicators:

Build.RequestedForEmail contains "copilot" or "github.com"
Build.SourceVersionMessage contains "copilot"
Build.RequestedFor contains "copilot"

🎯 Execution Strategy

For Copilot builds:

Run x64-linux first
Only run other triplets if x64-linux succeeds
Cancel remaining jobs if x64-linux fails

For regular builds:

Unchanged behavior - all triplets run in parallel

🏗️ Implementation

Restructured the pipeline into 3 stages:

stages:
- DetectBuildType    # Determines if build is Copilot-triggered
- BuildX64Linux      # Always runs x64-linux first  
- BuildAllOthers     # Conditionally runs other triplets

The key logic uses Azure Pipelines stage conditions:

condition: or(
  eq(dependencies.DetectBuildType.outputs['DetectCopilot.detect.IsCopilotBuild'], 'false'),
  succeeded('BuildX64Linux')
)

✅ Benefits

Resource Efficiency: Prevents pool overload for Copilot builds
Fast Feedback: Early failure detection saves time and resources
Zero Impact: Regular user workflows completely unchanged
Robust Detection: Multiple fallback mechanisms catch various Copilot scenarios

🧪 Testing Scenarios

Scenario	x64-linux	Other Jobs	Behavior
Copilot + Success	✅ Runs first	✅ Run after x64-linux	Serial execution
Copilot + Failure	❌ Fails	❌ Cancelled	Early termination
Regular Build	✅ Runs	✅ Run in parallel	Existing behavior

Fixes #45945.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: ras0219-msft <[email protected]>

ras0219-msft

Let's use a two stage approach:

A "scouting" stage. If the branch is not a copilot branch, this stage should do nothing and finish ASAP. If it is a copilot branch, this stage should build x64-linux.
A "full" stage. This stage depends on the scouting stage. If it is a copilot branch, it builds everything but x64-linux -- otherwise, builds everything.

ras0219-msft · 2025-06-12T17:47:05Z

scripts/azure-pipelines/azure-pipelines.yml

+    - script: |
+        echo "=== Copilot Build Detection ==="
+        echo "Checking build trigger and commit author..."
+        echo "Build.RequestedForEmail: $(Build.RequestedForEmail)"


Use the branch name to detect copilot -- copilot PRs are always prefixed with copilot/

Changed detection method to use branch name prefix copilot/ instead of email/commit message checks. The pipeline now uses startsWith(variables['Build.SourceBranch'], 'refs/heads/copilot/') for detection.

Commit: afab5b2

Co-authored-by: ras0219-msft <[email protected]>

Copilot · 2025-06-12T17:57:03Z

Let's use a two stage approach:

A "scouting" stage. If the branch is not a copilot branch, this stage should do nothing and finish ASAP. If it is a copilot branch, this stage should build x64-linu...

Implemented the two-stage approach as requested. The pipeline now has:

Scouting stage: Skips entirely for non-copilot builds, builds only x64-linux for copilot builds
Full stage: Builds everything except x64-linux for copilot builds, or everything for regular builds

Commit: afab5b2

BillyONeal · 2025-06-12T19:21:32Z

scripts/azure-pipelines/azure-pipelines.yml

-    vcpkgToolSha: ${{ parameters.vcpkgToolSha }}
-    tripletPattern: ${{ parameters.tripletPattern }}
+variables:
+  isCopilotBuild: ${{ startsWith(variables['Build.SourceBranch'], 'refs/heads/copilot/') }}


It might be worth checking the source repo as well as the branch name here.

BillyONeal · 2025-06-12T19:29:05Z

scripts/azure-pipelines/azure-pipelines.yml

+variables:
+  isCopilotBuild: ${{ startsWith(variables['Build.SourceBranch'], 'refs/heads/copilot/') }}
+
+stages:


Not sure how I feel about the introduction of stages as that causes funny UI effects in AzDO. In particular having a job which is sometimes in one stage and sometimes in the other can make comparing across builds painful.

But I also understand there may not be a better way to achieve this.

Is it possible to do something like

${{ if parameters.isCopilotBuild }}: dependsOn: x64_linux

repeated for each of the non-x64_linux jobs instead? That way the same job is always used, only whether they are dependencies or not matters.

Copilot initially implemented something like that, but I think it gave up because of concerns about runtime variables vs compile-time variables. Since this is branch based, I think it could be done with compile-time?

@copilot implement this approach.

Implemented the compile-time conditional approach using ${{ if startsWith(variables['Build.SourceBranch'], 'refs/heads/copilot/') }}: to conditionally add dependsOn: x64_linux to all non-x64_linux jobs. This avoids the stage-based approach and UI issues while achieving the same behavior. Commit: b5fecde

Co-authored-by: ras0219-msft <[email protected]>

ras0219-msft · 2025-06-12T23:13:50Z

scripts/azure-pipelines/azure-pipelines.yml

 - template: windows/azure-pipelines.yml
  parameters:
    jobName: x86_windows
    vcpkgToolSha: ${{ parameters.vcpkgToolSha }}
    tripletPattern: ${{ parameters.tripletPattern }}
+  ${{ if startsWith(variables['Build.SourceBranch'], 'refs/heads/copilot/') }}:


I believe this didn't work because the SourceBranch is different for PRs.

Let's use the Build.SourceBranchName instead:

Build.SourceBranchName The name of the branch in the triggering repo the build was queued for. Git repo branch, pull request, or tag: The last path segment in the ref. For example, in refs/heads/main this value is main. In refs/heads/feature/tools, this value is tools. In refs/tags/your-tag-name, the value is your_tag_name, with hyphens (-) replaced by underscores (_). TFVC repo branch: The last path segment in the root server path for the workspace. For example, in $/teamproject/main this value is main. TFVC repo gated check-in or shelveset build is the name of the shelveset. For example, Gated_2016-06-06_05.20.51.4369;[email protected] or myshelveset;[email protected]. Note: In TFVC, if you're running a gated check-in build or manually building a shelveset, you can't use this variable in your build number format.

Updated to use Build.SourceBranchName with copilot/ prefix instead of Build.SourceBranch with refs/heads/copilot/ prefix to fix detection for PR builds. Commit: 3a9ad27

Can we look at the pull request owner somehow? At least AzDO seems to know it but I don't know if it's exposed in the YAML

I think that should be possible, based on https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#how-are-the-identity-variables-set, however I'm concerned it won't be as robust as the branch name. GitHub explicitly documents the branch name as part of the security model:

https://docs.github.com/en/copilot/using-github-copilot/coding-agent/about-assigning-tasks-to-copilot#risk-copilot-can-push-code-changes-to-your-repository

Limits the permissions in access tokens used by Copilot. Pushes are only allowed to branches beginning with copilot/. Copilot cannot push to the main or master branches.

So I feel more confident that this will not change.

Azure Pipelines exposes Build.RequestedFor and Build.RequestedForId variables that contain information about who requested the build. For pull requests, Build.RequestedFor would contain the pull request author's name. We could potentially use this in addition to the branch name check, but the current approach using Build.SourceBranchName with copilot/ prefix should be sufficient for detecting Copilot-generated branches.

Co-authored-by: ras0219-msft <[email protected]>

ras0219-msft

Plumb dependsOn through the templates

ras0219-msft · 2025-06-13T16:45:03Z

scripts/azure-pipelines/azure-pipelines.yml

 - template: windows/azure-pipelines.yml
  parameters:
    jobName: x86_windows
    vcpkgToolSha: ${{ parameters.vcpkgToolSha }}
    tripletPattern: ${{ parameters.tripletPattern }}
+  ${{ if startsWith(variables['Build.SourceBranchName'], 'copilot/') }}:
+    dependsOn: x64_linux


The current PR adds dependsOn as a parameter to the template, but that doesn't result in a dependsOn field in the underlying jobs.

Fixed the issue by adding a dependsOn parameter to all template files and updating them to conditionally add the dependsOn field to the underlying jobs. The main pipeline now passes the dependsOn parameter to templates instead of trying to add it at the template level. Commit: aa5cd99

Co-authored-by: ras0219-msft <[email protected]>

Copilot · 2025-06-13T16:52:47Z

Plumb dependsOn through the templates

Added dependsOn parameter to all template files (linux, windows, osx, android) and updated the main azure-pipelines.yml to pass the parameter instead of trying to add it at the template level. The templates now properly handle the dependsOn parameter and conditionally add it to the job definition when specified. Commit: aa5cd99

ras0219-msft · 2025-06-19T20:29:46Z

scripts/azure-pipelines/azure-pipelines.yml

+#     tripletPattern: ${{ parameters.tripletPattern }}
+- job: A
+  pool:
+    vmImage: 'ubuntu-latest'


Change this to use the PrAnd-WUS pool.

Changed the pool to use PrAnd-WUS as requested. Commit: 0a4b7f7

Co-authored-by: ras0219-msft <[email protected]>

Initial plan for issue

aba21ed

Copilot AI assigned Copilot and ras0219-msft Jun 11, 2025

Copilot started work on behalf of ras0219-msft June 11, 2025 20:49 View session

Copilot AI and others added 2 commits June 11, 2025 21:03

Implement Copilot build detection and x64-linux first execution

8db8113

Co-authored-by: ras0219-msft <[email protected]>

Add detailed documentation and improve Copilot detection robustness

7b8a9be

Co-authored-by: ras0219-msft <[email protected]>

Copilot AI changed the title ~~[WIP] [Azure Pipelines] Copilot triggered workflows should run x64-linux first and abort on failure.~~ [Azure Pipelines] Implement Copilot build detection with x64-linux first execution Jun 11, 2025

Copilot AI requested a review from ras0219-msft June 11, 2025 21:07

Copilot finished work on behalf of ras0219-msft June 11, 2025 21:07

LilyWangLL added the category:infrastructure Pertaining to the CI/Testing infrastrucutre label Jun 12, 2025

ras0219-msft requested changes Jun 12, 2025

View reviewed changes

Copilot started work on behalf of ras0219-msft June 12, 2025 17:49 View session

Refactor to two-stage approach with branch name detection per feedback

afab5b2

Co-authored-by: ras0219-msft <[email protected]>

Copilot finished work on behalf of ras0219-msft June 12, 2025 17:57

BillyONeal reviewed Jun 12, 2025

View reviewed changes

Copilot started work on behalf of BillyONeal June 12, 2025 19:29 View session

Copilot stopped work on behalf of BillyONeal due to an error June 12, 2025 19:30
Copilot has encountered an internal error. Please try again later. If the problem persists, please contact GitHub Support, including the request ID `37C0:28E41:1DF687:2514B6:684B2AB6`.

Copilot started work on behalf of ras0219-msft June 12, 2025 21:12 View session

Implement compile-time conditional dependencies approach per feedback

b5fecde

Co-authored-by: ras0219-msft <[email protected]>

Copilot finished work on behalf of ras0219-msft June 12, 2025 21:21

ras0219-msft requested changes Jun 12, 2025

View reviewed changes

Copilot started work on behalf of ras0219-msft June 12, 2025 23:14 View session

Fix copilot branch detection for PRs using Build.SourceBranchName

3a9ad27

Co-authored-by: ras0219-msft <[email protected]>

Copilot finished work on behalf of ras0219-msft June 12, 2025 23:21

ras0219-msft requested changes Jun 13, 2025

View reviewed changes

Copilot started work on behalf of ras0219-msft June 13, 2025 16:45 View session

Plumb dependsOn parameter through all templates to fix job dependencies

aa5cd99

Co-authored-by: ras0219-msft <[email protected]>

Copilot finished work on behalf of ras0219-msft June 13, 2025 16:54

BillyONeal previously approved these changes Jun 18, 2025

View reviewed changes

printf debugging

aa88784

ras0219-msft dismissed BillyONeal’s stale review via aa88784 June 19, 2025 18:39

ras0219-msft added 3 commits June 19, 2025 18:51

printf debugging

6e51b8c

printf debugging

81ff2bd

printf debugging

47c2b30

ras0219-msft requested changes Jun 19, 2025

View reviewed changes

Copilot started work on behalf of ras0219-msft June 19, 2025 20:29 View session

Change pool to PrAnd-WUS as requested

44b4016

Co-authored-by: ras0219-msft <[email protected]>

Copilot AI requested a review from ras0219-msft June 19, 2025 20:32

Copilot finished work on behalf of ras0219-msft June 19, 2025 20:32

[Azure Pipelines] Implement Copilot build detection with x64-linux first execution #45946

Are you sure you want to change the base?

[Azure Pipelines] Implement Copilot build detection with x64-linux first execution #45946

Uh oh!

Conversation

Copilot AI commented Jun 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Solution

🔍 Copilot Detection

🎯 Execution Strategy

🏗️ Implementation

✅ Benefits

🧪 Testing Scenarios

Uh oh!

ras0219-msft left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jun 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Jun 12, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jun 12, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jun 12, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jun 13, 2025

Choose a reason for hiding this comment

Uh oh!

ras0219-msft left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jun 13, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Jun 13, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jun 19, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI commented Jun 11, 2025 •

edited

Loading