Why do builds fail?—A conceptual replication study

Barrak, Amine; Eghan, Ellis E.; Adams, Bram; Khomh, Foutse

doi:10.1016/j.jss.2021.110939

Cited by 11 publications

(5 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the other hand, researchers might be hindered to conduct their studies on a large variety of projects, or on multiple versions of a project. Several studies have investigated the causes of build failures, 13,31 while other studies have tried to devise approaches to tackle the underlying issues 73,74,31,75 . In an ideal world, creating an environment (e.g., a docker container) for building a large number of projects would benefit researchers to conduct studies that need to build projects as a prerequisite (e.g., dynamic analysis, measuring code coverage, etc.…”

Section: Discussionmentioning

confidence: 99%

“…However, the intensity of code review is different from the quality of the code review. Despite the fact that code review quality has been studied in many studies, there is no obvious way to quantitatively measure it 35,75,76 . Having a measurement of the quality of the code review would help researchers when comparing projects' code review and when studying its correlation with other quality assurance practices.…”

Section: Discussionmentioning

confidence: 99%

“…Despite the fact that code review quality has been studied in many studies, there is no obvious way to quantitatively measure it. 35,75,76 Having a measurement of the quality of the code review would help researchers when comparing projects' code review and when studying its correlation with other quality assurance practices. Also, with a code quality measurement practitioners have a concrete idea of the state of the quality of the code reviews taking place in their project, and it enables them to improve their code review practices.…”

Section: Measuring the Quality Of Code Reviewmentioning

confidence: 99%

See 2 more Smart Citations

State‐of‐the‐practice in quality assurance in Java‐based open source software development

Khatami,

Zaidman

2024

Softw Pract Exp

View full text Add to dashboard Cite

SummaryTo ensure the quality of software systems, software engineers can make use of a variety of quality assurance approaches, for example, software testing, modern code review, automated static analysis, and build automation. Each of these quality assurance practices have been studied in depth in isolation, but there is a clear knowledge gap when it comes to our understanding of how these approaches are being used in conjunction, or not. In our study, we broadly investigate whether and how these quality assurance approaches are being used in conjunction in the development of 1454 popular open source software projects on GitHub. Our study indicates that typically projects do not follow all quality assurance practices together with high intensity. In fact, we only observe weak correlation among some quality assurance practices. In general, our study provides a deeper understanding of how existing quality assurance approaches are currently being used in Java‐based open source software development. Besides, we specifically zoom in on the more mature projects in our dataset, and generally we observe that more mature projects are more intense in their application of the quality assurance practices, with more focus on their ASAT usage, and code reviewing, but no strong change in their CI usage.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Section: Measuring the Quality Of Code Reviewmentioning

confidence: 99%

See 1 more Smart Citation

State‐of‐the‐practice in quality assurance in Java‐based open source software development

Khatami,

Zaidman

2024

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…They developed and trained a nine-dimensional random forest model, which confirmed that build and author history and code complexity were the most important predictors of build failures [30].…”

Section: Related Workmentioning

confidence: 91%

Using Continuous Integration Techniques in Open Source Projects—An Exploratory Study

Wróbel,

Szymukowicz,

Weichbroth

2023

IEEE Access

View full text Add to dashboard Cite

For a growing number of software projects, continuous integration (CI) techniques are becoming an essential part of the process. However, the maturity of their adoption in open source projects varies. In this paper, we present an empirical study on GitHub repositories to explore the use of continuous integration techniques in open source projects. Following the Goal-Question-Metric (GQM) approach, 3 research questions and 7 metrics were defined for such a goal. We mined 10 repositories of open source projects with 101,149 pull requests, 399,671 commits from 20,432 developers. This was followed by exploratory data analysis for each metric. In summary, our results indicate that (RQ1) most failed CI builds required a small change in the pull request to fix the code; (RQ2) CI builds of smaller pull requests are more likely to succeed than larger ones; (RQ3) there was no correlation found between developer experience in committing to the project and the success rate of CI builds. Most of the projects studied have not yet developed a mature approach to using continuous integration techniques. In these cases, developers do not thoroughly test code before submitting pull requests. Furthermore, the results of the study confirmed that developers tend to submit pull requests with small amounts of new or modified code. INDEX TERMS continuous integration, mining software repositories, open source projects

show abstract

“…The literature reveals that a high degree of STC yields positive outcomes for project development concerning quick task resolution time [4], enhanced build quality [5], and improved project quality [6]. However, the misalignment of social and technical dependencies, known as the coordination gap, reduces productivity concerning a growing number of code changes [7], build failure, and low team performance [8].…”

Section: Introductionmentioning

confidence: 99%

Socio-Technical Congruence as an Emerging Concept in Software Development: A Scientometric Analysis and Critical Literature Review

et al. 2021

View full text Add to dashboard Cite

Ample evidence in the literature emphasizes using socio-technical congruence (STC) to address coordination issues in distributed software development. The recent decades have shown a progressive growth in STC, resulting in an increasing number of research studies in the scientific corpora. However, no existing study has systematically analyzed and illustrated the research patterns, latest trends, and evolution in STC. This study aims to explore the knowledge structure and create evolutionary trajectories from STC publications. To achieve this aim, a scientometric analysis is performed that combined a critical literature review (CLR) of STC-related published research in the Web of Science and Scopus databases from 2000 to 2020.The scientometric analysis is conducted through four scientometric techniques: i) coword network analysis, ii) co-author network analysis, iii) co-citation analysis, and iv) document clustering with timeline analysis. The study outcomes will help understand and visualize STC's research status quo. CLR is objectively conducted to recognize the latest research topics, themes, and salient features of STC research in software development. A total of 306 bibliographic data are analyzed to generate study-related networks and density visualizations. The results reveal an evolution in the STC field from its conception to the recent developments of STC models and other related factors. This study primarily contributes to the literature by providing a systematic view related to STC research to assist software practitioners in identifying applications and key research areas. Moreover, the combination of scientometric analysis and CLR reveals key researchers, journals and conferences, institutions, prominent contributing countries, and six major research themes, including "community structure" and "socio-technical congruence" as the most prominent ones.

show abstract

Why do builds fail?—A conceptual replication study

Cited by 11 publications

References 15 publications

State‐of‐the‐practice in quality assurance in Java‐based open source software development

State‐of‐the‐practice in quality assurance in Java‐based open source software development

Using Continuous Integration Techniques in Open Source Projects—An Exploratory Study

Socio-Technical Congruence as an Emerging Concept in Software Development: A Scientometric Analysis and Critical Literature Review

Contact Info

Product

Resources

About