分支、主干持续集成？
我正在努力与分支和主干结构建立良好的持续集成。
但我们应该如何思考呢？
我们希望我们的持续集成工具能够为我们提供一个每周测试一次的版本，该版本将保留一周，有时我们会进行错误修复直到发布。
我应该创建一个名为 Testbranch 的分支并让 testbranch 始终构建并放到测试服务器上吗？或者我应该从其他方向思考？
Im working to set up an good continuous integration with a branching and trunk structure.
But how should we think?
We want that our continuous integration tool to give us a version to test once a week which will stay at that version for a week, well sometimes we will do bugfixes until release.
Should I create a branch called like Testbranch and let the testbranch always been build and put up to the testserver? Or shall I think in any other direction?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为您应该在“测试/即将发布”分支和另一个监视主线的 CI 构建上构建 CI。
对测试分支的任何错误修复都将被构建并移至测试服务器。对主线的更改将仅通过您现有的任何类型的单元测试来构建。每周，您将同步主线和测试分支，这将触发测试分支上的构建以开始新功能的测试。
我还建议购买第二个测试服务器，以便您也可以定期部署主线并验证它是否正常运行。从长远来看，这可能会让您延长测试周期，以便立即测试更多“开发中”项目。这最终可能会让您的团队离开分支模型，只进行一周的冲刺，在一周内构建、测试和交付新功能。
I think you would have CI builds on both the "test / soon to be released" branch and another CI build that watches the mainline.
Any bug fixes to the test branch would be built and moved to the test server. Changes to the mainline would just be built with any sort of unit testing you have in place. Weekly, you would sync the mainline and test branches which would trigger a build on the test branch to start your testing of the new features.
I'd also recommend getting a second test server so you can deploy the mainline regularly as well and validate that it's on track. Over the long term, this may allow you to push up your test cycle so more "in development" items get tested immediately. This may eventually allow your team to leave the branching model and just have one week sprints where new functionality is built, tested and delivered in a single week.