Revision as of 12:08, 1 June 2024 edit Stevebroshar (talk \| contribs) Extended confirmed users 5,278 edits →Everyone commits to the baseline every day: 'committer' is not a thing (use developer); describe value in terms a non-programmer might understand; daily build is unrelated to frequent committing ← Previous edit		Revision as of 12:19, 1 June 2024 edit undo Stevebroshar (talk \| contribs) Extended confirmed users 5,278 edits Clarify goals/defn of CI; that CI includes build/test as a way to achieve the goal of ensuring codebase is in workable state Next edit →
Line 6: [[File:Continuous Integration.jpg\|thumb\|right\|Sketch of [[flow diagram]] for continuous integration]] '''Continuous integration''' ('''CI''') is the practice of integrating [[source code]] changes frequently and ensuring that the integrated codebase is in a workable state. '''Continuous integration''' ('''CI''') is the practice of frequently building and testing a [[software system]] during its development. It is intended to ensure that [[source code\|code]] written by [[programmers]] is always buildable, runnable and passes [[automated testing]]. Developers [[Merge (version control)\|merge]] to an [[Branching (revision control)\|integration branch]] and an automated system [[Software build\|builds]] and [[software testing\|tests]].<ref name="martinfowler" /> Typically, developers [[Merge (version control)\|merge]] changes to an [[Branching (revision control)\|integration branch]], and an automated system [[Software build\|builds]] and [[software testing\|tests]] the [[software system]].<ref name="martinfowler" /> Often, the automated process runs on each [[Commit (version control)\|commit]] or runs on a schedule such as once a day.

Continuous integration: Difference between revisions