版本控制和发布管理 [英] Version control and release management
问题描述
我曾经工作的大型机商店有一个自动化发布管理工具不仅控制对源的并发修改,而且还处理运行的编译器,预编译器,数据库绑定实用程序等,使其成为我们的全自动部署工具。
我的理解是,更现代化的版本控制工具只支持源管理部分。这个理解是否正确?
这是绝对不正确的。任何现代版本控制工具都支持预提交和后提交钩子,此时可以运行所需的任何代码。
在subversion中,我们使用后提交钩子
在我们实际的生产服务器中,我们有代码验证然后部署稳定的次要版本标签,因为他们致力于发行经理的回购。
Are there any so-called "version control systems" that also support actual release management / deployment ?
The mainframe shop I used to work for, had an automated release management tool that did not only control concurrent modifications to sources, but that also took care of running compilers, precompilers, database bind utilities etc. etc., making it our fully automated deployment tool as well.
My understanding is that "more modern" version control tools support only the source management part. Is that understanding correct ?
This is absolutely incorrect. Any modern version control tool supports both pre and post commit hooks, at which point you can run any code you want.
In subversion, we use the post-commit hook to deploy a copy of the app to the dev server every time a developer checks in code.
In our actual production servers, we have code that verifies and then deploys stable minor version tags as they are committed to the repo by the release managers.
这篇关于版本控制和发布管理的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!