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

查看:106
本文介绍了持续集成对于独立开发者来说是否重要?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我以前从来没有使用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.

好处是,你知道 - 当有人破坏构建。这意味着A)他们提交了代码,防止编译,这会拧紧任何一个更新,或B)他们提交的代码,打破了一些测试,这意味着他们介绍了一个需要修复的错误,或者测试需要更新以反映代码的变化。

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 who did an 'update', or 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屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆