Global variables at release management
At release management it would be great to use "globale" build varaibles. For example build path, build name, drop location. Also define variables at release template to use this for more custom tasks. Also fixed variables like, date, time and so on.
Maik van der Gaag commented
Saw that it is now availible for vNext release but please also add it to the standard releases.
Will you support global variables in Agent-Based Release Template?
Roopesh Nair commented
Here is the link to the feature
Roopesh Nair commented
Release Management Update 4 RC has enabled support for 'System variables' in vNext Release Templates.
You can also define configuration variables at Global, Server, Component, in Action or using configuration file as well
For list of new features in Update 4 RC, please refer to link
Claude Remillard commented
This is very high on our priority list and we are working on it.
Thanks for the feedback!
It would be very much useful to have the variable support.
Steve Fenton commented
We would love this feature at the deployment sequence level as there is a lot of repetition throughout a release at the moment, such as paths and connection strings.
Adam Bezverkov commented
We were surprised at the lack of variable support, since the template is very workflow-esqe, and the variable implementation in workflow would solve all of the problems that are deal breakers for us now. We have a couple dozen servers to deploy several apps to, and without variables, it becomes unmaintainable quickly. A simple example of one website with AppPool creation and roll back requires defining the same AppPool name 4+ times.
We need real variable support. We are having to hard code: c:\installdir\ in every step. (Creating service, changing credentials, creating website, etc etc) This will not scale out when we have multiple lower environments and a few dozen applications.
Greg (GMO LLC)
Peter Sarapkin commented
Surprisingly, but I see that most of people don't care about this important feature. And I've been surprised when I found that this feature is not supported. I have a proposal for Microsoft engineers, whatever the results of the vote will be - mark this feature as the high prioritized.
people have a problems due to lack of this feature.