Fix CI template test conflicts by implementing template isolation#63153
Closed
Fix CI template test conflicts by implementing template isolation#63153
Conversation
Co-authored-by: ilonatommy <32700855+ilonatommy@users.noreply.github.com>
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
Fix CI template test conflicts by implementing template isolation
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.
The CI job for local development validation was disabled due to conflicts with concurrent template tests. When both the Helix template tests and the local development validation job ran simultaneously, they would interfere with each other's template engine state, causing build failures.
Root Cause
The issue occurred because two different template testing workflows were accessing shared global state:
default-build.yml) already used proper isolation via--debug:custom-hiveci-public.yml) used global template installation in the user profileThis led to race conditions when both jobs tried to install/uninstall templates concurrently:
Solution
Modified
src/ProjectTemplates/scripts/Test-Template.psm1to use the same isolation strategy as the Helix template tests:Key improvements:
The solution mirrors the proven isolation pattern already used by Helix template tests, ensuring both workflows can run concurrently without conflicts.
Testing
condition: 'false'tocondition: 'true'Fixes #63149.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.