Continuous integration: Difference between revisions

Revision as of 12:31, 1 June 2024

Revision as of 12:40, 1 June 2024

Line 138:

{{More citations needed section|date=May 2016}}

CI benefits include:

Continuous integration is intended to produce benefits such as:

* Facilitates detecting bugs earlier

* Helps detect [[software bug|bugs]] early and facilitate fixing them due to smaller changesets

* Reduces effort to fix bugs found via automated integration testing

* Avoids build chaos that otherwise ensures at release time

* Avoids the chaos of integrating many changes

* When a test fails or a bug is found, reverting the codebase to a bug-freegood baselinestate entailsresults in fewer lost changes

* Frequent availability of a known-good build for testing, demo, and release

* Frequent code check-incommit encourages modular, less complex code<ref>{{Cite journal |last1=Junpeng |first1=Jiang |last2=Zhu |first2=Can |last3=Zhang |first3=Xiaofang |date=July 2020 |title=An Empirical Study on the Impact of Code Contributor on Code Smell |url=https://qrs20.techconf.org/download/QRS-IJPE/12_An%20Empirical%20Study%20on%20the%20Impact%20of%20Code%20Contributor%20on%20Code%20Smell.pdf |journal=International Journal of Performability Engineering |volume=16 |issue=7 |pages=1067–1077 |doi=10.23940/ijpe.20.07.p9.10671077|s2cid=222588815 }}</ref>

Continuous automated testing may include benefits:

* Quick feedback on system-wide impact of code changes

* Supports collection of [[Softwaresoftware metrics]] such as [[code coverage]], [[code complexity]], and [[feature complete]]ness can focus developers on developing functional, quality code, and help develop momentum in a team{{Citation needed|date=November 2009}}

== Costs ==