Install Extension step returns success after failing about azure-devops-extension-tasks HOT 3 CLOSED

from azure-devops-extension-tasks.

So what would be the preferred way of setting up a build pipeline that continuously builds an extension and automatically installs it on a set of accounts (creating a new version number for each build?

Is there any parameter to "install" to specify that we just want to update to a new version so we do not get that error?

from azure-devops-extension-tasks.

Your setup is fine. If the extension gets uninstalled, this task will reinstall it. But if the extension is installed to all accounts, it will remain so and the new version will automatically become available to these accounts.

The Share and Install task are there for convenience, should you decide to delete a private version of the extension from the marketplace, their default share and install status will be reset, these tasks will then restore them to what the pipeline expects. In every other case, they're not going to do anything, except complain that the extension has already been shared or has already been installed to the account.

I've built in logic to ignore these errors, awaiting a proper fix in tfs-cli. See also: #12.

from azure-devops-extension-tasks.