Continuous Integration in a Social-Coding World: Empirical Evidence from GitHub
Open accessThe DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
Continuous integration is a software engineering practice of frequently merging all developer working copies with a shared main branch, e.g., several times a day. With the advent of GitHub, a platform well known for its "social coding" features that aid collaboration and sharing, and currently the largest code host in the open source world, collaborative software development has never been more prominent. In GitHub development one can distinguish between two types of developer contributions to a project: direct ones, coming from a typically small group of developers with write access to the main project repository, and indirect ones, coming from developers who fork the main repository, update their copies locally, and submit pull requests for review and merger. In this paper we explore how GitHub developers use continuous integration as well as whether the contribution type (direct versus indirect) and different project characteristics (e.g., main programming language, or project age) are associated with the success of the automatic builds.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Handbook of Parametric and Nonparametric Statistical Procedures: Third Edition
Sheskin, D. J. (2003) · doi:10.1201/9781420036268 · Cited by 1,551
Lakhani, K. R., & Wolf, R. G. (2003) · doi:10.2139/ssrn.443040 · Cited by 1,531
Lakhani, K. R., & Wolf, R. G. (2005) · Perspectives on Free and Open Source Software · doi:10.7551/mitpress/5326.003.0005 · Cited by 1,530
Social coding in GitHub: transparency and collaboration in an open software repository
Dabbish, L., Stuart, C., Tsay, J., & Herbsleb, J. (2012) · Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work · doi:10.1145/2145204.2145396 · Cited by 999
An exploratory study of the pull-based software development model
Gousios, G., Pinzger, M., & Deursen, A. V. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568260 · Cited by 628 · cited 1×
“This continuous application of quality control checks aims to speed up the development process and to ultimately improve software quality, by reducing the integration problems occurring between team members that develop software collaboratively [1].”
Background
Cited by
Quality and productivity outcomes relating to continuous integration in GitHub
Vasilescu, B., Yu, Y., Wang, H., Devanbu, P., & Filkov, V. (2015) · Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2786805.2786850 · Cited by 406
Self-citationCurating GitHub for engineered software projects
Munaiah, N., Kroh, S., Cabrey, C., & Nagappan, M. (2017) · Empirical Software Engineering · doi:10.1007/s10664-017-9512-6 · Cited by 365
Systematic literature review on the impacts of agile release engineering practices
Karvonen, T., Behutiye, W., Oivo, M., & Kuvaja, P. (2017) · Information and Software Technology · doi:10.1016/j.infsof.2017.01.009 · Cited by 44
Metadata
- Authors
- Vasilescu, B., van Schuylenburg, S., Wulms, J., Serebrenik, A., & van den Brand, M. G. J.
- Venue
- 2014 IEEE International Conference on Software Maintenance and Evolution
- Publisher
- IEEE
- Published
- 2014-09
- Pages
- 401-405
- OpenAlex
- W2048499643
- Cited by
- 90
- References
- 5
- FWCI
- 7.41
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Continuous Integration in a Social-Coding World: Empirical Evidence from GitHub. https://app.cochat.ai/papers/10.1109/icsme.2014.62
- The paper
- Vasilescu, B., van Schuylenburg, S., Wulms, J., Serebrenik, A., & van den Brand, M. G. J. (2014). Continuous Integration in a Social-Coding World: Empirical Evidence from GitHub. 2014 IEEE International Conference on Software Maintenance and Evolution. https://doi.org/10.1109/icsme.2014.62
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.