You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got this strange issue when trying multiple times to get sources from a repo in a yaml pipeline.
This works if I use 'self' or a defined repository, but it doesn't work when using the following syntax:
Validation in the online designer doesn't give any response when trying to validate it and when I try to run the pipeline, it gives this error:
I also played around with different workspace cleaning and dependsOn settings, but that doesn't change the result.
Looks like an issue or am I doing something wrong?
(btw. we're using our own managed pools, don't know it that makes any difference)
I've attached a simple yaml file that produces the issue, __OwnManagedPool__ and __PathToRepository__ need to be replaced by a valid value. yaml-checkout-issue.zip
The text was updated successfully, but these errors were encountered:
Hi,
I've got this strange issue when trying multiple times to get sources from a repo in a yaml pipeline.
This works if I use 'self' or a defined repository, but it doesn't work when using the following syntax:
checkout: git://$(repositoryName)@$(repositoryBranch)
This issue occurs when this syntax is present more than once in the pipeline.
For example, this works:
and this also works;
But this doesn't:
Validation in the online designer doesn't give any response when trying to validate it and when I try to run the pipeline, it gives this error:
I also played around with different workspace cleaning and dependsOn settings, but that doesn't change the result.
Looks like an issue or am I doing something wrong?
(btw. we're using our own managed pools, don't know it that makes any difference)
I've attached a simple yaml file that produces the issue,
__OwnManagedPool__
and__PathToRepository__
need to be replaced by a valid value.yaml-checkout-issue.zip
The text was updated successfully, but these errors were encountered: