Reported by yan jingzhu Apr 18, 2017 at 10:00 AM tfs
In a release definition, I set Release name format value with :Release-$(Release.ReleaseDescription)-$(rev:r)
I got this: The $(Release.ReleaseDescription) could not be recognized in the top Release Definition Name /Release Name. But it was recognized in RELEASE_RELEASENAME.
The same issue here on both TFS 2017 and TFS 2017 UPDATE 1.
Thank you for your feedback. We have determined that this issue will not be addressed in the upcoming release. We will continue to evaluate it for future releases. Thank you for helping us build a better Visual Studio.
Added a solution by Anjani Chandan [MSFT] · Apr 24, 2017 at 01:51 AM
We are looking into it. We will update with our investigation.
Added a solution by Shashank Bansal [MSFT] · Apr 25, 2017 at 10:14 AM
Not all variables available for deployments can be used in release names.
The set of supported variables that can be used in the release name format mask is mentioned at https://www.visualstudio.com/en-us/docs/build/concepts/definitions/release/index#numbering.
Release.ReleaseDescription is not one of the supported variables in release names.
We've added a bug on our side to ensure the release name displayed in the task logs is same as the one actually generated using the release name format.
Are you planning to support release name variable in upcoming releases?
Added a solution by Alok Agrawal [MSFT] · Aug 18, 2017 at 08:45 AM
Thank you for your feedback! We have fixed this issue and it's available in the latest deployment of Visual Studio Team Services. Thank you for helping us build a better Visual Studio!
Team Explorer VS2013 TFS 2010 - TF30063
0
Solution
TFS 15 Changeset incorrectly associated to tasks automatically
2
Solution
TF30063 when changing Notification URL
2
Solution
Useful to allow tasks to be 'unassigned'
0
Solution
Cannot add TFS server group to Access Level
1
Solution
Build definition content not appearing in browser-based log
4
Solution
TFS10158 error when using shelveset picker to queue new build
2
Solution
unable to see build step logs, tfs 2017
2
Solution
TFS 2017, Users at Stakeholder access level doesn't have search box
3
Solution
Discussion work item lookup using # fails in project with custom process template
0
Solution