A Brief Study on Build Failures in Continuous Integration: Causation and Effect
A Brief Study on Build Failures in Continuous Integration: Causation and Effect
复制标题
持续集成中构建失败的简要研究：因果关系
DOI：
10.1007/978-981-13-0224-4_2
复制
发表时间：
2018
期刊：
影响因子：
--
通讯作者：
Bharavi Mishra
中科院分区：
文献类型：
--
作者：
Romit Jain;Saket Singh;Bharavi Mishra
持续集成（CI）成功地解决了错误修复问题，因此在软件开发人员中获得了广泛的欢迎。 CI 鼓励随时随地提交，以便每个错误都可以追溯到其来源并进行相应处理。然而，CI 的核心仍然是一种实践，并且只能实现其中的一部分。任何不遵循良好 CI 实践的行为都会导致更多的构建失败。 CI 的连续性可能会导致大团队混乱，导致一个开发人员的构建失败而导致另一个开发人员的构建失败。多次连续的构建失败可能会使项目陷入停滞，直到构建干净为止，这可能会导致开发人员最终失去兴趣。在本文中，我们研究了 CI 中构建失败的因果关系。我们首先看看较大的团队规模是否会导致更多的构建失败，其次，不断增加的连续构建失败是否会对开发人员的生产力产生任何影响。我们使用 TravisTorrent 中提供的数据并分析了 3,702,595 个 Travis 版本，其中大部分使用 Java 和 Ruby 作为所使用的编程语言。对于这两种语言，我们都对我们要解决的问题进行了全面的分析。
Continuous Integration (CI) has successfully tackled the problem of bug fixing owing to which it has gained immense popularity among software developers. CI encourages to commit on the go so that each bug can be traced to its source and handled accordingly. However, CI remains a practice at its core, and only a part of it can be implemented. Anything which does not follow good CI practice would pave the way for a greater number of build fails. CI’s continuous nature may cause a clutter in a big team, leading to one developer’s build failing the other. Numerous consecutive build fails can put the project on a standstill till the build is made clean which may cause developers to lose interest eventually. We investigate, in this paper, causation and effect of build failure in CI. We first see whether a large team size contributes to more build failure and second, whether an increasing number of consecutive build failures have any impact on the productivity of developers. We have used data provided in TravisTorrent and analysed the 3,702,595 Travis builds which mostly contain Java and Ruby as the programming language used. For both the languages, we have made a comprehensive analysis of the problem we address.