Configuring global and local variables for a release
Variables are used to store values that need to be passed into tasks during the release. There are various advantages of using variables over hardcoding these values directly in tasks:
Variables support encrypting values in a way that they cannot be seen or changed by users of a release definition
Storing values in variables helps avoid duplication
Variables can be shared across all environments
Variables can be shared across all tasks within a specific environment
In this recipe, you'll learn how to configure release and environment variables for a release definition.
Getting ready
To edit a release definition, you need to be a member of the Release Administrators Group. These permissions are also available to the Project Administrators Group.
Scenario: The FabrikamTFVC Team uses Azure blob storage for storing files that are needed by the FabrikamTFVC Web release definition. The Team would like the ability to access the blob storage connection...