Re-enable Windows local development validation CI job#63150
Closed
Re-enable Windows local development validation CI job#63150
Conversation
Co-authored-by: ilonatommy <32700855+ilonatommy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] CI template tests are not passing at the same time as local developmnet validation tests
Re-enable Windows local development validation CI job
Aug 6, 2025
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
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.
This PR re-enables the Windows local development validation CI job that was previously disabled due to conflicts with template tests.
Problem
The "Windows local development validation" job in
.azure/pipelines/ci-public.ymlwas disabled withcondition: 'false'because it was causing CI failures when running concurrently with other template test jobs. This job is critical for validating local development workflows including:Root Cause Analysis
Investigation revealed that this job was the only CI job that actually runs project template tests via
./src/ProjectTemplates/build.cmd. Other CI jobs explicitly avoid template test conflicts by using/p:RunTemplateTests=falsein their build arguments. The conflict occurred because multiple jobs were attempting to run template tests simultaneously, causing resource contention.Solution
The fix is minimal and surgical - simply remove the disabling condition to re-enable the job. This is safe because:
/p:RunTemplateTests=falseto disable template testsChanges Made
Validation
The re-enabled job will now run template tests independently without interfering with other concurrent CI jobs.
Fixes #63149.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.