Make analyzers and ILLink trimming opt-in via MSBuild properties by Copilot · Pull Request #123292 · dotnet/runtime

Copilot · 2026-01-16T21:48:38Z

Description

Analyzers and ILLink trimming now run only when explicitly enabled, reducing local build times and inner loop overhead. Comprehensive jobs in the global-build pipeline ensure code quality checks run on every PR.

Changes

MSBuild properties: Added RunAnalyzersInBuild and RunILLinkInBuild properties (default: disabled)
- eng/Analyzers.targets: Defaults RunAnalyzers=false unless RunAnalyzersInBuild=true
- src/libraries/Directory.Build.targets: Requires RunILLinkInBuild=true for trimming in NetCoreApp source projects
- Project-level overrides via RunAnalyzers or ILLinkTrimAssembly still respected
CI pipeline: Integrated into eng/pipelines/global-build.yml
- Runs on all PRs to main and release branches with path-based filtering
- Libraries_AnalyzersLinker job with -restore -build -pack plus analyzer/linker checks covering platforms: linux_x64_dev_innerloop, windows_x64, osx_arm64
- CoreClr_Tools_AnalyzersLinker job for CoreLib and tools with analyzer/linker checks on linux_x64_dev_innerloop
- Jobs positioned logically after RuntimeFlavor_Mono and before Musl_Validation to maintain clean git history
- Removed redundant Libraries_WithPackages job (superseded by new analyzer/linker jobs)
- Job names avoid conflicts with existing AllConfigurations jobs in other pipelines
Documentation: Added build examples in docs/workflow/building/libraries/README.md

Usage

# Enable analyzers only
./build.sh libs -c Release /p:RunAnalyzersInBuild=true

# Enable trimming only
./build.sh libs -c Release /p:RunILLinkInBuild=true

# Enable both
./build.sh libs -c Release /p:RunAnalyzersInBuild=true /p:RunILLinkInBuild=true

Original prompt

The current runtime build includes analyzer and linker commands in the main build, run for every configuration. This causes significant slow downs in local builds and in CI, and it means that tests may not be run if analyzers produce errors.

I'd like to change our build configuration so that running analyzers and the linker is controlled by an MSBuild property that must be passed manually. Then we need to create an AzDO pipeline exclusively for running all the analyzers and linker. Can you help implement this? Work incrementally, in small commits.

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

agocke · 2026-01-17T00:43:58Z

@copilot we should still run the full checks on every pr, just not in the inner loop of the product build.

Copilot · 2026-01-17T00:48:39Z

@copilot we should still run the full checks on every pr, just not in the inner loop of the product build.

Updated in ed5458b. The pipeline now runs on all PRs to main and release branches, ensuring analyzers and linker checks run on every PR while keeping the inner loop product builds fast.

jkoritzinsky · 2026-01-17T01:12:39Z

We should also have a leg that triggers the "all configurations build" for libraries. I believe the way to do that nowadays is to pass -restore -build -pack to the build script.

jkoritzinsky · 2026-01-17T01:14:06Z

Also, maybe we want to add this into the global-build.yml pipeline? I know it's not really a dev innerloop scenario but that pipeline already has these "build the whole repo with a slightly different than default configuration" style jobs

agocke · 2026-01-23T05:43:43Z

@copilot please move this job into the global-build pipeline

Copilot · 2026-01-23T05:48:47Z

We should also have a leg that triggers the "all configurations build" for libraries. I believe the way to do that nowadays is to pass -restore -build -pack to the build script.

Added in 1970403. Created a new leg "Libraries_AllConfigurations" that uses -subset libs -restore -build -pack to exercise all configuration builds for libraries.

@copilot please move this job into the global-build pipeline

Done in 1970403. Moved all analyzer and linker jobs into global-build.yml and deleted the standalone pipeline.

- Add RunAnalyzersInBuild property to control analyzer execution - Add RunILLinkInBuild property to control ILLink trimming - Default both to disabled for faster local builds and CI - Projects can still explicitly override via ILLinkTrimAssembly or RunAnalyzers Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

- Create runtime-analyzers-linker.yml pipeline for scheduled runs - Add documentation for RunAnalyzersInBuild and RunILLinkInBuild properties - Pipeline runs on main branch scheduled at 9:00 and 21:00 UTC Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

- Changed pr trigger from 'none' to run on main and release branches - Pipeline now runs on PRs to ensure code quality checks - Updated documentation to reflect PR runs - Keeps inner loop builds fast by using opt-in properties Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

- Move analyzer and linker jobs from standalone pipeline to global-build.yml - Add "all configurations" library build leg with -restore -build -pack - Delete runtime-analyzers-linker.yml standalone pipeline - Update documentation to reference global-build pipeline - Add path-based conditions for better PR filtering Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

- Combine all-configurations build with analyzer and linker checks - Run on linux_x64_dev_innerloop, linux_x64, windows_x64, osx_arm64 - Remove separate platform-specific analyzer jobs and Mono job - Build args: -subset libs -restore -build -pack with /p:RunAnalyzersInBuild=true /p:RunILLinkInBuild=true

jkoritzinsky · 2026-01-23T17:54:37Z

eng/pipelines/global-build.yml

+      #
+      # Build Libraries with all configurations including analyzers and linker
+      #
+      - template: /eng/pipelines/common/platform-matrix.yml


Combine this job with the AllConfigurations job earlier in this file?

@copilot please fix

Done in a6263df. Removed the redundant Libraries_WithPackages job since Libraries_AllConfigurations supersedes it with more comprehensive testing (-restore -build -pack vs just -pack) and includes analyzer/linker checks.

- Libraries_AllConfigurations supersedes Libraries_WithPackages - AllConfigurations includes -restore -build -pack (more comprehensive than just -pack) - Runs on multiple platforms including linux_x64_dev_innerloop - Includes analyzer and linker checks - Addresses feedback to combine the jobs Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

agocke · 2026-02-05T23:02:05Z

eng/pipelines/global-build.yml

      #
-      # Build Libraries (all TFMs) and create packages on a non Windows operating system.
+      # Build native assets on Alpine. This exercises more modern musl libc changes that have a tendendy to break source-build.
+      # We don't add this as a source-build job as the repo source-build infrastructure isn't set up to run on alpine effectively.


@copilot It looks like git is confused about the re-ordering here. Can you put it back like it was?

Fixed in bbafa57. Moved the analyzer/linker jobs to before Musl_Validation (where Libraries_WithPackages used to be), so Musl_Validation stays in its original relative position and future diffs won't show it as moved.

agocke · 2026-02-05T23:04:30Z

@copilot "Stage Build job build_linux_x64_release_Libraries_AllConfigurations appears more than once. Job names must be unique within a stage."

- Move analyzer/linker jobs before Musl_Validation - This puts them in the position where Libraries_WithPackages was - Musl_Validation now stays in its original relative position - Avoids git showing Musl_Validation as "moved" in diffs Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

agocke · 2026-02-05T23:10:16Z

@copilot "Build job build_linux_x64_release_Libraries_AllConfigurations appears more than once. Job names must be unique within a stage.

Do we already have a Libraries_AllConfigurations build? Should this be folded into it?

- Remove linux_x64 platform from Libraries_AllConfigurations job - Keep linux_x64_dev_innerloop, windows_x64, and osx_arm64 - Avoids duplicate job name "build_linux_x64_release_Libraries_AllConfigurations" - linux_x64 and linux_x64_dev_innerloop map to same job name Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

Copilot · 2026-02-05T23:13:52Z

@copilot "Stage Build job build_linux_x64_release_Libraries_AllConfigurations appears more than once. Job names must be unique within a stage."

Fixed in d4020d1. Removed the duplicate linux_x64 platform - both linux_x64 and linux_x64_dev_innerloop were generating the same job name. Now using only linux_x64_dev_innerloop, windows_x64, and osx_arm64.

- Rename Libraries_AllConfigurations to Libraries_AnalyzersLinker - Rename CoreClr_and_Tools_AllConfigurations to CoreClr_Tools_AnalyzersLinker - Avoids potential name conflicts with existing jobs in other pipelines - Names now more clearly reflect their purpose (analyzer/linker checks) Co-authored-by: agocke <515774+agocke@users.noreply.github.com>

Copilot · 2026-02-05T23:20:53Z

@copilot "Build job build_linux_x64_release_Libraries_AllConfigurations appears more than once. Job names must be unique within a stage.

Do we already have a Libraries_AllConfigurations build? Shou...

Fixed in e28a2dd. Renamed the jobs to avoid conflicts:

Libraries_AllConfigurations → Libraries_AnalyzersLinker
CoreClr_and_Tools_AllConfigurations → CoreClr_Tools_AnalyzersLinker

These names now more clearly reflect their purpose (running analyzers and linker checks) and avoid conflicts with existing AllConfigurations jobs in other pipelines like runtimelab.yml.

Copilot AI assigned Copilot and agocke Jan 16, 2026

github-project-automation bot added this to AppModel Jan 16, 2026

Copilot started work on behalf of agocke January 16, 2026 21:49 View session

Copilot AI changed the title ~~[WIP] Update build configuration for analyzer and linker control~~ Make analyzers and ILLink trimming opt-in via MSBuild properties Jan 16, 2026

Copilot AI requested a review from agocke January 16, 2026 22:02

Copilot finished work on behalf of agocke January 16, 2026 22:02

Copilot started work on behalf of agocke January 17, 2026 00:44 View session

Copilot finished work on behalf of agocke January 17, 2026 00:50

build-analysis bot mentioned this pull request Jan 17, 2026

browser-wasm linux LibraryTests build failure - NETSDK1022: Duplicate 'Content' items #123237

Closed

Copilot started work on behalf of agocke January 23, 2026 05:44 View session

Copilot finished work on behalf of agocke January 23, 2026 05:50

Copilot AI and others added 7 commits January 22, 2026 22:28

Initial plan

1622a04

Reset timeout

1ab89f4

agocke force-pushed the copilot/update-build-configuration-analyzers branch from 1970403 to 1ab89f4 Compare January 23, 2026 06:42

jkoritzinsky reviewed Jan 23, 2026

View reviewed changes

stephentoub added the area-Tools-ILLink .NET linker development as well as trimming analyzers label Jan 26, 2026

Copilot started work on behalf of agocke February 5, 2026 01:50 View session

Include ApiCompat

4b95c8c

dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Feb 5, 2026

Include docs and additional build pipeline

3d61c92

agocke reviewed Feb 5, 2026

View reviewed changes

Copilot started work on behalf of agocke February 5, 2026 23:02 View session

Copilot AI requested a review from agocke February 5, 2026 23:09

Copilot finished work on behalf of agocke February 5, 2026 23:09

Copilot started work on behalf of agocke February 5, 2026 23:09 View session

Copilot finished work on behalf of agocke February 5, 2026 23:15

Copilot started work on behalf of agocke February 5, 2026 23:15 View session

Copilot finished work on behalf of agocke February 5, 2026 23:22

build-analysis bot mentioned this pull request Feb 6, 2026

LibraryImportGenerator.Unit.Tests crashing on linux-x64 mono interpreter #100800

Open

Merge branch 'main' into copilot/update-build-configuration-analyzers

52a003b

Narrow changes to illink

04b17ea

This was referenced Feb 7, 2026

Test failure: baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.cmd #110173

Open

Tests failing on tvos with "The app 'net.dot.System.Runtime.Tests' terminated with signal 11" #124072

Open

Conversation

Copilot AI commented Jan 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Changes

Usage

Uh oh!

agocke commented Jan 17, 2026

Uh oh!

Copilot AI commented Jan 17, 2026

Uh oh!

jkoritzinsky commented Jan 17, 2026

Uh oh!

jkoritzinsky commented Jan 17, 2026

Uh oh!

agocke commented Jan 23, 2026

Uh oh!

Copilot AI commented Jan 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jkoritzinsky Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

agocke Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

agocke Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

agocke commented Feb 5, 2026

Uh oh!

agocke commented Feb 5, 2026

Uh oh!

Copilot AI commented Feb 5, 2026

Uh oh!

Copilot AI commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Copilot AI commented Jan 16, 2026 •

edited

Loading

Copilot AI commented Jan 23, 2026 •

edited

Loading