arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 1907.01602cs.SE
收藏

持续集成剧院

Continuous Integration Theater

Wagner Felidré, Leonardo Furtado, Daniel da Costa, Bruno Cartaxo, Gustavo Pinto

摘要:

背景:持续集成(CI)系统现在是一些软件开发实践的基础。一些工具,如TravisCI,CircleCI和Hudson,实现CI实践,通常被软件工程师采用。然而,软件工程师使用这些工具的方式可能会导致我们所说的“持续集成剧场”,即软件工程师不能有效地使用这些工具,从而导致不健康的CI实践。目的:本文的目标是了解这些不健康的持续集成实践在实践中的普遍程度。方法:通过检查1,270个使用TravisCI(最常用的CI服务)的开源项目,我们定量研究了使用CI的常见程度(1)不频繁提交,(2)在测试覆盖率差的软件项目中,(3)长期保持中断的构建,以及(4)运行时间过长的构建。结果:我们观察到748个($sim$ 60%)项目面临不频繁的提交,这基本上使合并过程更加困难。此外,我们能够找到51个项目的代码覆盖率信息。平均代码覆盖率为78%,尽管Ruby项目的代码覆盖率高于Java项目(分别为86%和63%)。然而,我们也发现了一些覆盖率非常小的项目($sim$ 4%)。尽管如此,我们观察到85%的研究项目至少有一个损坏的构建,需要超过四天的时间才能修复。有趣的是,非常小的项目(多达1,000行代码)是修复损坏的构建所需时间最长的项目。最后,我们注意到,对于大多数被研究的项目,构建都是在10分钟的经验法则下执行的。结论:我们的研究结果是很重要的软件工程师越来越多的社区,采用CI的做法,每天的基础上,但可能不知道的不良做法,最终采用。

英文摘要:

Background: Continuous Integration (CI) systems are now the bedrock of several software development practices. Several tools such as TravisCI, CircleCI, and Hudson, that implement CI practices, are commonly adopted by software engineers. However, the way that software engineers use these tools could lead to what we call "Continuous Integration Theater", a situation in which software engineers do not employ these tools effectively, leading to unhealthy CI practices. Aims: The goal of this paper is to make sense of how commonplace are these unhealthy continuous integration practices being employed in practice. Method: By inspecting 1,270 open-source projects that use TravisCI, the most used CI service, we quantitatively studied how common is to use CI (1) with infrequent commits, (2) in a software project with poor test coverage, (3) with builds that stay broken for long periods, and (4) with builds that take too long to run. Results: We observed that 748 ($sim$60%) projects face infrequent commits, which essentially makes the merging process harder. Moreover, we were able to find code coverage information for 51 projects. The average code coverage was 78%, although Ruby projects have a higher code coverage than Java projects (86% and 63%, respectively). However, some projects with very small coverage ($sim$4%) were found. Still, we observed that 85% of the studied projects have at least one broken build that take more than four days to be fixed. Interestingly, very small projects (up to 1,000 lines of code) are the ones that take the longest to fix broken builds. Finally, we noted that, for the majority of the studied projects, the build is executed under the 10 minutes rule of thumb. Conclusions: Our results are important to an increasing community of software engineers that employ CI practices on daily basis but may not be aware of bad practices that are eventually employed.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑