连续集成的投资回报率是多少？ [英] 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的第一个原因是，它有助于防止开发人员检查破碎的代码，有时会削弱整个团队。想象一下，如果我在离开假期之前进行一个涉及某些数据库模式更改的重要签入。当然，一切工作正常在我的dev盒，但我忘记签入db模式更改脚本可能或可能不是微不足道。嗯，现在有一个复杂的变化，指的是数据库中的新的/更改的字段，但没有人在第二天在办公室实际上有这个新的模式，所以现在整个团队都下来，而有人看着复制你已经做的工作​​，只是忘了签到。

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.

是的，我使用一个特别讨厌的例子与数据库更改，但它可以是任何东西，真的。也许部分签入一些电子邮件代码，然后导致所有的开发人员垃圾邮件的实际最终用户？你的名字...

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屋！