Knowledge Tree
continuous integration
Also known as: CI, continuous integration pipelines
Facts (12)
Sources
A Mixed-Methods Study of Open-Source Software Maintainers On ... arxiv.org Feb 3, 2025 5 facts
claimThe study 'A Mixed-Methods Study of Open-Source Software Maintainers On ...' identifies limited automation, vulnerability scoring, and missing continuous integration (CI) processes or features as particularly challenging and understudied aspects of platform security features for open-source software (OSS) maintainers.
referenceThomas Rausch, Waldemar Hummer, Philipp Leitner, and Stefan Schulte performed an empirical analysis of build failures in the continuous integration workflows of Java-based open-source software, published in the 2017 IEEE/ACM 14th International Conference on Mining Software Repositories (MSR).
referenceFiorella Zampetti, Simone Scalabrino, Rocco Oliveto, Gerardo Canfora, and Massimiliano Di Penta authored the study 'How open source projects use static code analysis tools in continuous integration pipelines,' published in the 2017 IEEE/ACM 14th International Conference on Mining Software Repositories (MSR).
claimOSS maintainers face challenges with Private Security Fixes (PSFs) because the built-in private vulnerability reporting feature on GitHub lacks Continuous Integration (CI) processes for developing fixes on private forks.
procedureTo mitigate the lack of CI processes in private forks, OSS maintainers often host additional private repositories outside of GitHub that mimic their public presence or run potential fixes through build processes on personal machines.
Best practices for version control to enhance development workflows harness.io Mar 17, 2025 2 facts
procedureContinuous Integration (CI) in version control involves configuring a repository to automatically run a suite of tests every time new code is pushed to provide immediate feedback on regressions.
procedureCode quality in version control can be enforced by using automated tools such as linters, formatters, and security scanners, and by integrating continuous integration pipelines to run tests before merging.
Open-source software - Wikipedia en.wikipedia.org 1 fact
procedureThe process of open-source software development proceeds in the following steps: (1) requirements elicitation via communication with the community (bug reporting, mailing lists, project pages), (2) task selection and solution identification, (3) code development and commitment, (4) peer testing and review, (5) code evolution through continuous integration feedback, (6) partial release and documentation once leadership and community are satisfied, and (7) project freezing for final release with only serious bug or security fixes.
Governance of open source software: state of the art - Springer Nature link.springer.com Jun 9, 2007 1 fact
referenceThe article 'Governance of open source software: state of the art' cites the 2003/4 paper 'Continuous integration and quality assurance: A case study of two open source projects' by J. Holck and N. Jørgensen, which studies continuous integration and quality assurance in open source.
[PDF] A Mixed-Methods Study of Open-Source Software Maintainers On ... usenix.org 1 fact
claimLimited automation, vulnerability scoring, and missing continuous integration (CI) processes are identified as significant challenges in the context of the study on open-source software maintenance and security.
Construction of Knowledge Graphs: State and Challenges - arXiv arxiv.org 1 fact
claimQuality problems in knowledge graphs can aggravate over time due to the continuous integration of additional data if they are not handled.
Building Leadership in an Open Source Community linuxfoundation.org 1 fact
procedureThe 12 recommended best practices for innersourcing are: (1) Improve testing methods, automate it, and make it an integral part of the development process; (2) Enforce peer review and implement tools to automate the practice; (3) Make source code accessible to everyone in your organization; (4) Adopt development tools with collaboration support built into it; (5) Adopt the “Release Early and Often” philosophy (shorter, more frequent releases); (6) Invest time and effort into building scalable and modular architectures that allow code re-use; (7) Adopt a continuous integration approach; (8) Encourage fluid and open communication, and practice it; (9) Improve documentation practices and use it as an additional means for quality assurance; (10) Make it possible for people to commit code even though they are not part of the project; (11) Increase transparency of decision making process (establish trust); (12) Empower individuals according to their contributions (meritocracy).