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.
We are happy to let you know that we have addressed this suggestion for vnext templates.
Here is the link to the feature: http://msdn.microsoft.com/en-us/library/dn834972.aspx
For Agent based templates
We have reviewed this and we will not be able to complete this suggestion in the foreseeable future.
For the Release Management service on Visual Studio Online this is planned. We are excited to let you know that we are working on this. We’ll keep you posted.
This is somewhat disappointing. Some companies are still using onsite versions of Team Foundation Server and without the support of Global Variables Release Management is not a viable solution.
Are Microsoft trying to steer us all to vnext instead of agent based?
Dan Holmes commented
I agree with the anonymous comment below: This needs to be added to the Agent-Based release templates as well. We have also been waiting for this for over a year and were disappointed not to see it in the 2015 released version.
Why you so investing the vNext and not investing in Agent-Based.
2 minutes to develop it to the Agent-Based and it was not done over a year!!!!
Encryption would be great as well, but mainly the Global variables issue is the only hold back from getting this going. Do we know if this will be in 2015 for Agent Based deployments?
Murat Tüfekçioğlu commented
We need this with out agent-based releases. Also encryption with values.
Yep, not having these available in Agent-based is really a severely limiting aspect of this tool.
Naeem Sarfraz commented
Please, please, please can we have this for Agent-based deployments
We need Global Variables support for "Agent based" deployments (NOT vNext)
Roopesh Nair commented
Roopesh Nair commented · October 27, 2014 02:10 · Flag as inappropriate
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
David R Brown commented
Claude Remillard - Any updates available for the implementation of Global Variables?
Reynaldo Zabala (RAZOREDGE) commented
Nevermind, that is NOT available for Agent based release templates...
Reynaldo Zabala (RAZOREDGE) commented
Christopher, are you able to get this to work in an agent based release template/ I've tried $(ApplicationPath) and $ApplicationPath and they are always null. I"m using Release Management Server 2013 Release 4.0 and I cannot get a value for ApplicationPath.
Christopher Haws commented
A handy hidden feature in Release Management is that you can use all of your TFS build variables inside of the arguments section of a component. So if you make a new component, inside of the Deployment Tool's Arguments, if you put $(TeamProject), Release Management will pick that variable up from the TFS Build. We use this to pass TFS Build parameters to scripts in release management.
Need and sorely missed for aqent-based release templates.
Leon Bouquiet commented
Also, for the Standard releases, please include the release *name* as one of the build variables, so that I can create a backup directory based on that. Right now I'm using a timestamp-based name for the backup directory, but this makes it hard to roll back a release using these backups over multiple servers.
we really need this feature available for Standard releases. When will this be coming?
Not complete - please make system variables available to standard releases, not just vNext. The original request did not limit the feature to vNext.
when this feature will be avaiable?
it will help me so much!!
do you have another suggestion how to use the environment name in configuration variables?
Maik van der Gaag commented
Saw that it is now availible for vNext release but please also add it to the standard releases.