Update the location of .autoManagedVhd marker file #5415
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Context
Azure DevOps is one of the major AutoManagedVHD customers, and one of their pipelines performs a “changed files” check inside the repository.
Previously, the .autoManagedVhd marker file was created inside the sources directory, which caused that step to incorrectly detect the marker as a modified file. This issue could easily impact other customers with similar checks.
To avoid interfering with repository-level file-change detection, it is safer and more correct to place the marker file in the parent directory of the sources directory. This still allows the agent to reliably detect that the existing working directory originates from an AutoManagedVHD.
Description
This PR updates the detection logic so the .autoManagedVhd marker file is looked up in the parent directory of the repository instead of inside it.
Risk Assessment (Low / Medium / High)
The change only applies when a .autoManagedVhd file is present and does not affect normal checkout scenarios.
Unit Tests Added or Updated (Yes / No)
No