TFS 2017.1 Release name format using $(Release.ReleaseDescription) causes RELEASE_RELEASENAME variable inconsistent

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.

releasename.png (77.4 kB)

Add comment Show 4

nicolas nguyen · Apr 18, 2017 at 02:47 PM 0

we have the same issue

Carlos Henrique Guardão Gandarez · Apr 20, 2017 at 12:50 PM 0

The same issue here on both TFS 2017 and TFS 2017 UPDATE 1.

Cezar Pimentel · Apr 20, 2017 at 04:48 PM 0

Same issue here.

Shashank Bansal [MSFT] · Apr 25, 2017 at 10:20 AM 0

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.

Add comment · Share

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.

Add comment Show 1 · Share

Carlos Henrique Guardão Gandarez · Apr 25, 2017 at 11:36 AM 0

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!

Add comment · Share

Developer Community

Get help from our community supported forum

TFS 2017.1 Release name format using $(Release.ReleaseDescription) causes RELEASE_RELEASENAME variable inconsistent

Solutions

Try Microsoft Edge

Developer Community

Get help from our community supported forum

TFS 2017.1 Release name format using $(Release.ReleaseDescription) causes RELEASE_RELEASENAME variable inconsistent

Solutions

Related Problems