As the documentation states, the Unlink is listed exactly where is says it should be. But I've looked and looked, and I can't find any way to link new parameters other than using variable groups (which you can then use via things like $(variableName)). The documentation states that there is a Link option next to the task's argument, but I can't find that anywhere. And if you unlink a parameter, the only way to get it back is to remove the stage entirely, and use the a template to get you back to the defaults again.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
I'm specifically looking the IIS Web App Deploy task, if that helps
This "Link" button is missing from both TFS 2018.2 and Azure DevOps Server 2019 RC1
Issue persists in Azure DevOps Server 2019 RTM.
This is still an issue.
This is completely and utterly useless. There is no way in Azure DevOps to add new process parameters. All I can do is unlink all. What a piece of garbage feature. How on earth can this be in production???
The link and unlink functionality is available for build pipelines only. They aren't available for release pipelines. We'll get the docs fixed to reflect the same.
That doesn't make sense though. If you create a brand new release pipeline, and for example pick/apply the template "IIS website deployment", you will see that it has 5 different parameters linked. So obviously the feature is there, and is used/supported. It just doesn't expose the ability for the user to manage those links.
There's UI for disconnecting all 5 parameters in this case, but not for disconnecting individual ones, or re-establishing any of those links after you've removed them.
Yes, you are right. the feature was never fully implemented in release. Process parameters that you see in release are shipped out of the box. Option create was not exposed to end users.
There were a few design challenges in the approach and the work was stalled. Some of the release tasks have visibility rules that change the inputs dynamically and it doesn't play well with process parameters feature. We will not be able to enable it in release until we have a clean solution to handle this.
At this point in time we are working issues, features that impact broader set of customers and we will not able to prioritize this.