非凡的发布流程是什么样的？
非凡的发布流程是什么样的？
我问这个问题是因为我们不断遇到与发布相关的生产问题。例如： - 不应该发布的代码被发布了 - 在测试服务器上运行的代码不在生产服务器上运行 - Ops 生成生产警报，但每个人都忽略它
有关此主题的书籍、文章、博客等的指针会有所帮助。
What does an extraordinary release process look like?
I ask because we keep having release related production problems. For example:
- Code that was not supposed to be released is released
- Code that runs on the test server does not run on the production server
- Ops generates an alert for production but everyone ignores it
Pointers to books, articles, blogs, etc. on this topic would be helpful.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我想说，如果您没有使用版本控制，并且您正在使用版本控制研究分支和标记，那么第一步是开始使用版本控制。使用分支，您可以将未准备好生产的代码保留在生产中，直到准备好为止，并且仅在准备好时才将其合并到主干中。
这可能是防止您提到的问题的最重要的事情之一。
书籍：
http://www.pragprog.com/titles/svn /pragmatic-version-control-using-subversion
http ://www.pragprog.com/titles/tsgit/pragmatic-version-control-using-git
乔尔测试：
http://www.joelonsoftware.com/articles/fog0000000043.html
一旦您获得了版本控制处于保密状态，您应该有很长的路要走才能避免您提到的问题。
I'd say the fist step is to start using version control if your not, and if you are using version control research branching and tagging. Using branching you can keep code that isn't production ready out of production till it is ready, and only merge it into trunk when it is.
This is probably one of the single most important things to prevent the issues your mentioning.
Books:
http://www.pragprog.com/titles/svn/pragmatic-version-control-using-subversion
http://www.pragprog.com/titles/tsgit/pragmatic-version-control-using-git
The Joel Test:
http://www.joelonsoftware.com/articles/fog0000000043.html
Once you get your version control under wraps, you should be a long ways towards avoiding the problems you mention.
我认为我们在当前项目中使用的开发流程非常好，直到我开始阅读 持续交付 作者：Jez Humble 和 David Farley。本书解释了如何使用版本控制、持续集成、配置管理、环境管理和自动化单元/验收/容量测试，只需按一下按钮即可部署最复杂的系统。这是一本很棒的读物。
I thought the development process we use on my current project was pretty good until I started reading Continuous Delivery by Jez Humble and David Farley. This book explains how even the most complicated systems can be deployed at the push of a button using version control, continuous integration, configuration management, environment management and automated unit/acceptance/capacity testing. It is a great read.