持续集成对于独立开发者来说重要吗? [英] Is Continuous Integration important for a solo developer?

问题描述

我以前从未使用过 CI 工具，但从我所读到的内容来看，我不确定它是否会给不每天编写代码的独立开发人员带来任何好处.

I've never used CI tools before, but from what I've read, I'm not sure it would provide any benefit to a solo developer that isn't writing code every day.

首先 - CI 对任何项目都有什么好处?

First - what benefits does CI provide to any project?

第二 - 谁应该使用 CI?它是否对所有开发者都有好处?

Second - who should use CI? Does it benefit all developers?

推荐答案

CI 的基本概念是，您有一个系统，每次有人提交版本控制系统时，您都会构建代码并运行自动化测试.这些测试将包括单元和功能测试，甚至是行为驱动测试.

The basic concept of CI is that you have a system that builds the code and runs automated tests everytime someone makes a commit to the version control system. These tests would include unit and functional tests, or even behavior driven tests.

这样做的好处是，当有人破坏了构建时，您可以立即知道.
这意味着:

The benefit is that you know - immediately - when someone has broken the build.
This means either:

一个.他们提交了阻止编译的代码，这会搞砸任何人

A. They committed code that prevents compilation, which would screw any one up

B.他们提交的代码破坏了一些测试，这意味着他们引入了需要修复的错误，或者需要更新测试以反映代码中的更改.

B. They committed code that broke some tests, which either means they introduced a bug that needs to be fixed, or the tests need to be updated to reflect the change in the code.

如果您是独立开发人员，如果您养成了在提交前运行测试的良好习惯，那么 CI 就相当有用，而这是您应该> 正在做.话虽如此，您可能会养成让 CI 为您进行测试的坏习惯.

If you are a solo developer, CI isn't quite as useful if you are in a good habit of running your tests before a commit, which is what you should be doing. That being said, you could develop a bad habit of letting the CI do your tests for you.

作为一个单独的程序员，它主要归结为纪律.使用 CI 是一项有用的技能，但您要避免养成任何不会转化为团队环境的坏习惯.

As a solo programmer, it mainly comes down to discipline. Using CI is a useful skill to have, but you want to avoid developing any bad habits that wouldn't translate to a team environment.

这篇关于持续集成对于独立开发者来说重要吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！