I have read this https://learn.microsoft.com/en-us/vsts/build-release/concepts/library/variable-groups but didn't find an answer..
Is it possible to use variables as values in another variable definiton?
Example:
MyCopyToFolder = C:\TFS_deploy_target\
MyConfigReplacements = $(MyCopyToFolder)ReplacementFolder\MyAppReplacements.ps1
I didn't find any word about that (im)possibility..
Yes, it's supported since TFS 2015 update4.
I just checked that, everything works as expected with the variables expanded on TFS 2018. Reference below screenshot.
Refer to the similar thread : Visual Studio Team Foundation Server 2015 release configuration variables not setting
Related
I have VS 2017 and VS 2019 installed on my computer. When I compare my changed code in VS 2019 Team Explorer's Pending Changes window, the differences are shown in VS 2017. That is as soon as I choose Compare with Latest Version option from context menu, VS 2017 is started and differences are shown in VS 2017. Is it something that I have to change in VS 2019 settings or VS2109 is supposed to work like this?
No, it's not an expected behavior.
Have tested VS2019 with either VS2017 or VS 2015 installed, both worked properly.
This strange behavior may related to cache. I was wondering if your target Path used to open under VS2017 in your environment. Or something cached in VS2017.
Please try to clear TFS cache and VS cache which may do the trick. First with TFS cache, if not work then with VS cache.
I know i can link my variable group stored in Library into a Release Definition, but my build definition doesn't have an option to link the variable group. I see it is available in TFS 2018. We are not upgrading our Prod instance from TFS 2017 anytime sooner. Is there any out of box method/way that i can link and read the library group?
Is there any out of box method/way that i can link and read the library group?
Sorry for any inconvenience.
I am afraid there is no such out-of-the-box method to link variable group in TFS 2017 Build definition.
There were many user voices about it before, and this request is resolved at Team Foundation Server 2018, MS team has no plans to apply it to TFS2017:
Variable group support
Variable groups have been available to use in release definitions, and now they are ready to be used in build
definitions, too. Learn more about creating a variable group. This has
been developed and prioritized based on related suggestions for
project-level build/release variables and variable groups in build
definitions.
And, AFAIK, there is currently no better workaround to solve this issue for TFS 2017.
So, we have to repeatedly define variables for each build pipeline before updating our TFS to 2018.
Hope this helps.
I was able to get TFS 2017 variable groups in JSON format. I'm now loading the JSON and instantiate the library groups.
http://tfsinstance/collectionname/teamproject/_apis/distributedtask/variablegroups/
Idea is to encapsulate this as a custom task and fetch required variable groups in the build definitions.
Variable group,in tfs 2017, are available only in release :(
In respect to the following question Is there a way to easily share Workspace settings (folder mappings) for Visual Studio Online / Team Foundation Server? and an entry I found regarding to this topic https://social.msdn.microsoft.com/Forums/vstudio/en-US/c9b16b30-4534-4781-a2e8-fb413a2df0af/power-tools-for-tfs-2017-with-vs-2017-rc?forum=tfsgeneral I wanted to ask if anyone knows how to achieve this very much needed functionality in TFS 2017?
Thanks.
Unfortunately we cannot create the workspace templates with VS 2017 for now.
According to release notes it says most of the previous Power Tools have been integrated into TFS 2017 that means no separate power tools for TFS 2017.
But the Team Utilities feature component is not integrated, that means these haven't shipped for Visual Studio 2017.
I have submitted a user voice here for you to suggest this feature, you can go and vote it up to achieve it in future.
Another similar thread for your reference: Team Members Team Utilities section in VS 2017
I've defined custom arguments in my xaml build script and provided values:
Then In my build I get the following instead of actual TF_BUILD_BUILDDIRECTORY. This is the string that writes: "dotCover Report..."
String.Format("dotCover Report Path: {0}\{1}", DotCoverReportPath, DotCoverReportFileName)
It's not translating to actual BUILDDIRECTORY path. What am I doing wrong? I've hit "refresh" several times and still no go. I wanted to get "C:\temp..." etc
Possible duplicate with this case TFS How to GetEnvironmentVariable value. You can't use $TF_BUILD_BUILDDIRECTORY in a custom build process.
Please refer more detailed info about how to use it from this blog Using Environment Variables in Visual Studio 2013 and TFS 2013
I was setting up a new build definition today and noticed there is an option 'Copy build output to the following Source Control folder'. I don't believe I have seen this before. It appears to me from searching google that it might be new as of TFS 11 (AKA TFS 2012) which I do not have installed on my system (or any system in my company network to my knowledge). My company uses TFS 2010 right now.
I went to another user who is able to view build definitions and it also was present when the build definitions were viewed.
This is what i see:
My questions:
1) Was this a part of TFS 2010 and I am just not remembering seeing it?
2) If this IS part of TFS 2010, how to enable this option (it is disabled).
3) If this is NOT a part of TFS 2010, how did it get there?
Yes, it is part of TFS 2010, but I have no idea how it got here!
I believe this is for those who use TFS 'as a service' (when you
have no file share to copy it to). According to
how-can-i-copy-build-output-to-the-source-control-folder
I have this in TFS/VS 2010 (SP1):