The core activities of CI are developers co-locate code changes in a shared, integration area frequently and that the resulting integrated codebase is verified for correctness. The first part generally involves merging changes to a common version control branch. The second part generally involves automated processes including: building, testing and many other processes.
A [[Server (computing)|server]] builds from the integration branch frequently. Usually this is after each commit or periodically like once a day.
Once builtTypically, alla tests[[Server should(computing)|server]] runbuilds from the integration area frequently; i.e. after each commit or periodically like once a day. The server may perform [[quality control]] checks such as running unit tests<ref>{{Cite web |title=Continuous integration |url=https://www.atlassian.com/agile/continuous-integration |last=Radigan |first=Dan |website=Atlassian Agile Coach}}</ref> and collect [[software quality]] metrics via processes such as static analysis and performance testing.
The server may also run other [[quality control]] and [[software quality]] processes such as static analysis, measuring performance, extracting documentation from the source code, and facilitating manual [[Quality assurance|QA]] processes.
