At the company I'm currently working we thought about using such an approach. In the end we chose to use something simpler. We let the automated builds set a label after a successful build and we have a tool that we use to sync to that label. So when someone breaks the build, other people will still be able to get a working version from the repository. The tool that syncs also makes sure that if you just submitted something, your changes will not be replaced by the revisions belonging to the label. For us this work perfectly, but it might not be suited for your situation.
发布评论
评论（2）
TeamCity 具有预测试提交功能。
http://www.jetbrains.com/teamcity/delayed_commit.html
TeamCity has a pretest commit feature.
http://www.jetbrains.com/teamcity/delayed_commit.html
在我目前工作的公司，我们考虑过使用这种方法。 最后我们选择使用更简单的东西。 我们让自动化构建在成功构建后设置一个标签，并且我们有一个工具可以用来同步到该标签。 因此，当有人破坏构建时，其他人仍然可以从存储库中获取工作版本。 同步工具还可以确保，如果您刚刚提交了某些内容，您的更改不会被属于该标签的修订所替换。 对于我们来说，这非常有效，但可能不适合您的情况。
问候，
塞巴斯蒂安
At the company I'm currently working we thought about using such an approach. In the end we chose to use something simpler. We let the automated builds set a label after a successful build and we have a tool that we use to sync to that label. So when someone breaks the build, other people will still be able to get a working version from the repository. The tool that syncs also makes sure that if you just submitted something, your changes will not be replaced by the revisions belonging to the label. For us this work perfectly, but it might not be suited for your situation.
Regards,
Sebastiaan