-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while executing task from yaml build pipeline #126
Comments
Googling the GUID led me to this one, which somebody else installed in our tenant. Leaving this issue open for now, since I also see others running into this; |
Hi @jsteenbeek - thanks for the info. According to this doc correct way to disambiguate is to qualify the task like so:
but this doesn't seem to work. I'm getting some help from the Product Group and will respond here (and in my readme) about how to disambiguate correctly. |
@jsteenbeek Finally got this figured out - there is an (undocumented) required field for the fully qualified name. To disambiguate, either use the GUID of the task (which would look nasty) or use:
I'm going to update my docs to include this too! |
Works like a charm, thanks! |
Also, if someone is using the other one and end up here this should help ReplaceTokens@3
|
Same here. I faced issue with message:
|
First of, thanks for all you do Colin. ReplaceTokens is one of our most used tasks!
When using the ReplaceTokens task from a yaml build pipeline I get the message that the task name is ambiguous, and Azure DevOps is unable to distinguish between tasks "a8515ec8-7254-4ffd-912c-86772e2b5962" and "9240b5c1-a1b2-4799-9325-e071c63236fb".
Not sure where the other task is coming from, 9240b5c1-a1b2-4799-9325-e071c63236fb is yours.
As a workaround I can refer to the task by the name '9240b5c1-a1b2-4799-9325-e071c63236fb@1'. The editor doesn't like it, but it gets picked up by the build correctly.
The text was updated successfully, but these errors were encountered: