Fix issue with workspaceRepo: true in Azure Pipelines
#171
Conversation
This file contains 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
added 3 commits
February 14, 2025 01:52
dzhukovsky
requested review from
alxmancini,
pippolino,
Saturate,
tlogik and
a team
as code owners
|
Hi @dzhukovsky thanks for the PR. I'll take a look at the code soon, but I'm a bit busy this week. |
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.
Description
This PR resolves an issue occurring when using
The problem was caused by the use of
Build.SourcesDirectory, which does not work correctly in a multi-repo setup withworkspaceRepo: true.Changes made
Build.SourcesDirectorywithBuild.Repository.LocalPathto correctly reference the repository path.__dirnameusage, as withworkspaceRepo: true, the current directory is already the repository root, whereasBuild.SourcesDirectoryin a multi-repo setup points one level above.This fix ensures proper handling of paths when using multi-repo checkouts in Azure Pipelines.