使用配置文件进行发布管理部署 [英] using config files for Release managent deployments
问题描述
我们目前对24种不同的应用程序使用相同的部署过程。 除了下面列出的特定环境变量之外，与发布过程没有任何区别。 我想将这些特定于环境的变量
添加到每个应用程序中的配置文件中，并根据部署到的环境将它们拉入发布过程。
我见过我们可以在发布模板本身中设置特定于环境的变量，但我更倾向于使用配置文件来创建应用程序并维护1个发布模板而不是24个不同的模板。
目前是否可行使用VS版本管理或可能的未来增强功能。 如果是最新信息，我们将非常感谢您对该过程的任何见解。
特定发布
- 应用程序名称
- 部署路径
- BuildNumber
特定于站点或环境（可以是以下任何DEV，QA，BETA，UAT，PROD1，PROD2 （DR）） - 站点和应用程序确定以下内容将在配置文件中或从数据库中提取：
- 服务器 - 可能是多个
- 服务帐户
提前感谢您提供任何帮助这个
< blockquote>
嗨mjlln，
感谢您在此发帖。
>>但我更愿意使用配置文件来处理应用程序并维护1个版本模板而不是24个不同版本。
让我们确认你的问题首先，你想要变量 和t继承值列在.config文件中，并在发布期间从该文件中获取值。然后，您只能使用一个模板进行发布。
在发布管理中无法达到此目的。我建议您可以在TFS Web访问中使用新版本功能正在使用TFS 2015 Update1和更新版本。在新版本功能中，您还需要为每个
环境配置变量。但是你可以克隆环境非常方便。
We currently use the same process of deployment for 24 different applications. Other than specific environment variables, listed below, there are no differences with the release process. I would like to add these environment specific variables to a config file within each application and pull them in to the release process based on the environment being deployed to.
I have seen that we can setup environment specific variables within the release template itself, but I would much rather use the config file for the application and maintain 1 release template versus 24 different ones.
Is this currently possible with VS Release management or possibly a future enhancement. If current, any insight into the process would be greatly appreciated.
Release specific
- Application name
- Deployment path
- BuildNumber
Site or Environment specific (can be any of the following DEV, QA, BETA, UAT, PROD1, PROD2 (DR)) - the site and application determine the following which would be in a config file or pulled from a db:
- Server(s) - this could be multiple
- Service Account
Thank you in advance for any assistance with this
Hi mjlln,
Thank you for posting here.
>>but I would much rather use the config file for the application and maintain 1 release template versus 24 different ones.
Let's confirm your question first, you want the variables and their values are listed in the .config file and get values from that file during release. Then you could use only one template for release.
This couldn't be reached in the Release Management. I suggest that you could use the new release feature in TFS web access if you are using TFS 2015 Update1 and newer version. In the new release feature, you also need to configure variable for each environment. But it is very convenient that you could clone environment.
这篇关于使用配置文件进行发布管理部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
