使用SVN和TeamCity的Web应用程序部署工作流程 [英] Web Application Deployment Workflow with SVN and TeamCity
问题描述
将有三个分支：
- 开发（ / trunk） - 整个ASP.NET解决方案，包括Web部署项目。
- 分段（/ branches / staging） - Web部署项目输出（仅执行文件 - bin，.aspx ，图像等）
- 部署（/ branches / deployment） - 与分段相同
CI进程：
- 提交中继线上的源更改。
- TeamCity检测到更改，构建解决方案并运行单元测试。
- 如果所有测试通过，TeamCity将Web部署项目输出提交到分支/分段，并将其导出到分段Web服务器上的wwwroot。
然后当我准备好部署到生产时，我将手动执行以下操作：
- 合并分支/分行/分行/生产
- 更新生产Web服务器的分支/生产工作副本。
这是否有意义？在这个过程中，有什么像VSS的用户可能会丢失/误解吗？
我写了一个很长的发布如何做到这一点与ASP.Net和Web部署项目 - 听起来你的胡同（不知道我是否被允许发布 - mods？）：
I'm fairly new to Subversion. Most of my work so far has been with Visual Source Safe. I'm looking to improve my deployment process with SVN and TeamCity. This is my plan:
There would be three branches:
- Development (/trunk) - Entire ASP.NET solution, including a Web Deployment Project.
- Staging (/branches/staging) - Web Deployment Project output (files needed for execution only - bin, .aspx, images, etc)
- Deployment (/branches/deployment) - same as Staging
The CI process:
- Commit source changes in trunk.
- TeamCity detects the change, builds the solution and runs unit tests.
- If all tests pass, TeamCity commits Web Deployment Project output to branches/staging and exports it to wwwroot on the staging web server.
Then when I'm ready to deploy to production, I'll do the following manually:
- Merge branches/staging with branches/production
- Update production web server's working copy of branches/production.
Does this make sense? Is there anything that a VSS user like myself might be missing/misunderstanding in this process?
I've written a pretty long post on how to do this with ASP.Net and web deployment projects - sounds right up your alley (don't know if I'm allowed to post this - mods?):
这篇关于使用SVN和TeamCity的Web应用程序部署工作流程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
