Split internal pipeline on exp and prod #12397
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR splits the internal Azure Pipeline configuration to separate experimental/performance builds from production builds. The change addresses previous pipeline failures in experimental builds by creating dedicated pipeline configurations with different validation settings.
Key changes:
- Creates a new dedicated experimental/performance pipeline with reduced validation requirements
- Removes experimental branch triggers from the main production pipeline
- Adds signing configuration overrides to handle NGEN validation issues in experimental VS insertions
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| azure-pipelines/vs-insertion-experimental.yml | Updates pipeline references from 'MSBuild' to 'MSBuildExpPerf' to consume the new experimental pipeline |
| azure-pipelines/.vsts-dotnet-exp-perf.yml | Creates new experimental/performance pipeline with simplified validation settings |
| azure-pipelines/.vsts-dotnet-build-jobs.yml | Extracts common build job definitions into reusable template with parameterized features |
| Directory.Build.targets | Adds signing configuration overrides for test signing to prevent NGEN validation issues |
| .vsts-dotnet.yml | Removes experimental branch triggers and refactors to use the new build jobs template |
Comments suppressed due to low confidence (1)
surayya-MS
approved these changes
Aug 22, 2025
JanProvaznik
approved these changes
Aug 22, 2025
JanProvaznik
pushed a commit
that referenced
this pull request
Aug 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempt 2 for #12126
The previous one was reverted due to problems with exp pipelines.
Now it got resolved with some tweaks around package validation in VS tests.
validated in scope of https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/663724