VSTS Name change in Azure DevOps effects on Git repositories

As I blogged in the past, it is super easy to build a VSTS Build (Now Azure DevOps Pipeline) to keep two repositories in sync. In that article one of the step is pushing the new code to the destination repositories with an url like: https://$(token)@myaddress.visualstudio.com/DefaultCollection, to automatically include a token to authenticate in the destination repository.

Now some of my build started to fail due to timeout and I immediately suspected the reason: the name change from VSTS to Azure DevOps changed the base url from accountname.visualstudio.com to dev.azure.com/accountname, and this in some way broke the bulid.

Due to rebranding of VSTS into Azure DevOps and change of Url you need to pay attention if some extension or build broke due to usage of the old url.

The solution is Super Simple, you need to go to the Repository page of your account using new dev.azure.com address and find the new address of the repository, something like: https://[email protected]/accountname/teamproject/_git/repositoryName.  You just need to change adding a semicolon and valid auth token after the accountname , so it is now like this: https://organization:$(Token)/dev.azure.

Figure 1: New string format to push force to a destination repository

Since I have many mirror build, I want a centralized way to securely store the token value to have all the build take this value from a centralized location; the obvious solution is a variable group linked to this build.

Figure 2: Variable group linked to this build.

In the variable group I have a single variable called Token, that is secure and it is used by many builds, so each time the token expire, I can change this and all the builds will use the new value.

Figure 1: A simple variable group that contains a single secure variable.

That’s all.

Gian Maria.