All geek questions in one place

How do you use Team Foundation Build to create multiple environments?

When you use Team Foundation Build to create a project for multiple environments, do you build one assembly for all environments or keep a separate script assembly for each environment?

Think about when I want the version of the workspace on my build server to create DEBUG mode for QA mode and RELEASE for UAT. Should one request build both of these assemblies, or should I make a build for QA when I need a build of QA, and make a build for UAT (using a label) when I need a build of UAT?

One caveat may be that we might want the assembly to be automatically copied to the server for one environment, and not another. Perhaps we want the bits to go to the QA, not the UAT, or we want the bits to go to the UAT, not the QA.

Let me know if you need to clarify.
Mark

+3
source share
2 answers

Will you always or almost always want to simultaneously create a QA and UAT release? If so, it makes sense to build them in one project. If not, I would separate them.

There may be other things that you want to take into account (additional tasks for specific purposes, which may be specific to one assembly or another), but if you decide to create both of them, it’s quite easy to set up in your assembly project. Just add a second section ConfigurationToBuild.

<ConfigurationToBuild Include="Debug|Any CPU">
    <FlavorToBuild>Debug</FlavorToBuild>
    <PlatformToBuild>Any CPU</PlatformToBuild>
</ConfigurationToBuild>
<ConfigurationToBuild Include="Release|Any CPU">
    <FlavorToBuild>Release</FlavorToBuild>
    <PlatformToBuild>Any CPU</PlatformToBuild>
</ConfigurationToBuild>
+3
source

, Release, _PublishedWebsites. 5 Builds 5 . TFS Release.

+1

Source: https://habr.com/ru/post/1705366/

More articles:


All Articles