How Open Source Projects Use Static Code Analysis Tools in Continuous Integration Pipelines
The DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.
Abstract
Static analysis tools are often used by software developers to entail early detection of potential faults, vulnerabilities, code smells, or to assess the source code adherence to coding standards and guidelines. Also, their adoption within Continuous Integration (CI) pipelines has been advocated by researchers and practitioners. This paper studies the usage of static analysis tools in 20 Java open source projects hosted on GitHub and using Travis CI as continuous integration infrastructure. Specifically, we investigate (i) which tools are being used and how they are configured for the CI, (ii) what types of issues make the build fail or raise warnings, and (iii) whether, how, and after how long are broken builds and warnings resolved. Results indicate that in the analyzed projects build breakages due to static analysis tools are mainly related to adherence to coding standards, and there is also some attention to missing licenses. Build failures related to tools identifying potential bugs or vulnerabilities occur less frequently, and in some cases such tools are activated in a "softer" mode, without making the build fail. Also, the study reveals that build breakages due to static analysis tools are quickly fixed by actually solving the problem, rather than by disabling the warning, and are often properly documented.
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
Expectations, outcomes, and challenges of modern code review
Bacchelli, A., & Bird, C. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606617 · Cited by 650
Why don't software developers use static analysis tools to find bugs?
Johnson, B., Song, Y., Murphy-Hill, E., & Bowdidge, R. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606613 · Cited by 568
(2013) · doi:10.5555/2486788.2486882 · Cited by 437
Usage, costs, and benefits of continuous integration in open-source projects
Hilton, M., Tunnell, T., Huang, K., Marinov, D., & Dig, D. (2016) · Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/2970276.2970358 · Cited by 342
Cited by
(2018) · doi:10.1145/3180155.3180209 · Cited by 98
Committed to Trust: A Qualitative Study on Security & Trust in Open Source Software Projects
Wermke, D., Wöhler, N., Klemmer, J. H., Fourné, M., Acar, Y., & Fahl, S. (2022) · 2022 IEEE Symposium on Security and Privacy (SP) · doi:10.1109/sp46214.2022.9833686 · Cited by 42
Do as I Do, Not as I Say: Do Contribution Guidelines Match the GitHub Contribution Process?
Elazhary, O., Storey, M.-A., Ernst, N., & Zaidman, A. (2019) · 2019 IEEE International Conference on Software Maintenance and Evolution (ICSME) · doi:10.1109/icsme.2019.00043 · Cited by 42
“While we followed the process outlined by Zampetti et al. [19], we do note that some repositories may not have included a CI tool configuration file yet still use a CI tool.”
MethodEnterprise-Driven Open Source Software: A Case Study on Security Automation
Angermeir, F., Voggenreiter, M., Moyon, F., & Mendez, D. (2021) · 2021 IEEE/ACM 43rd International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip52600.2021.00037 · Cited by 30
“[20] conducted a study, which focused specifically on the usage of static code analysis tools in CI pipelines.”
Background
Metadata
- Authors
- Zampetti, F., Scalabrino, S., Oliveto, R., Canfora, G., & Di Penta, M.
- Venue
- 2017 IEEE/ACM 14th International Conference on Mining Software Repositories (MSR)
- Publisher
- IEEE
- Published
- 2017-05
- Pages
- 334-344
- OpenAlex
- W2646484260
- Cited by
- 122
- References
- 4
- FWCI
- 11.22
- Type
- conference paper
- Language
- en
- Open access
- closed
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
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.