持续集成的投资回报率是多少? [英] What’s the ROI of Continuous Integration?

问题描述

目前，我们的组织没有实施持续集成.

Currently, our organization does not practice Continuous Integration.

为了让我们启动并运行 CI 服务器，我需要制作一份说明投资回报的文档.

In order for us to get an CI server up and running, I will need to produce a document demonstrating the return on the investment.

除了通过及早发现和修复错误来节省成本之外，我很好奇我可以在本文档中坚持的其他好处/节省.

Aside from cost savings by finding and fixing bugs early, I'm curious about other benefits/savings that I could stick into this document.

推荐答案

我喜欢 CI 的第一个原因是它有助于防止开发人员检查有时会削弱整个团队的损坏代码.想象一下，如果我在去度假之前进行了涉及一些数据库模式更改的重要签到.当然，在我的开发盒上一切正常，但我忘记签入数据库模式更改脚本，这可能是微不足道的，也可能不是微不足道的.好吧，现在有一些复杂的更改涉及数据库中的新/更改字段，但是第二天在办公室的人实际上没有那个新模式，所以现在整个团队都倒下了，而有人正在研究复制你已经做过的工作并且只是忘记签到了.

My #1 reason for liking CI is that it helps prevent developers from checking in broken code which can sometimes cripple an entire team. Imagine if I make a significant check-in involving some db schema changes right before I leave for vacation. Sure, everything works fine on my dev box, but I forget to check-in the db schema changescript which may or may not be trivial. Well, now there are complex changes referring to new/changed fields in the database but nobody who is in the office the next day actually has that new schema, so now the entire team is down while somebody looks into reproducing the work you already did and just forgot to check in.

是的，我使用了一个特别糟糕的 db 更改示例，但它可以是任何东西，真的.也许部分签入带有一些电子邮件代码，然后导致您的所有开发人员向您的实际最终用户发送垃圾邮件?你给它起名字...

And yes, I used a particularly nasty example with db changes but it could be anything, really. Perhaps a partial check-in with some emailing code that then causes all of your devs to spam your actual end-users? You name it...

因此，在我看来，避免其中一种情况将使这种努力的投资回报率很快得到回报.

So in my opinion, avoiding a single one of these situations will make the ROI of such an endeavor pay off VERY quickly.

这篇关于持续集成的投资回报率是多少?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！