Unit
- Definition: Continuous Integration is a software development practice where developers merge their code changes into a central repository several times a day, with each merge verified by an automated build and test process.
- Origin: The concept was popularized by the Extreme Programming methodology in the late 1990s, emphasizing early and continuous feedback to reduce integration risks.
- Core principle: Integrate frequently, ideally multiple times per day, to detect integration errors as quickly as possible.
- Automated verification: Each integration triggers a build that compiles code, runs unit tests, and performs static analysis, ensuring the new code does not break existing functionality.
- Version control: CI relies on a shared version control repository (e.g., Git) with a branching strategy that facilitates frequent merging.
- Feedback loop: Rapid feedback from CI pipelines allows developers to fix issues immediately while context is fresh, reducing the cost of defects.
- Cultural shift: CI requires a culture of collective ownership, where developers take responsibility for the health of the main branch and fix broken builds as a priority.
- Tool support: Modern CI tools like Jenkins, GitLab CI/CD, GitHub Actions, and CircleCI automate the pipeline orchestration and provide visibility into build status.
Code Example
YAML
# Simple GitHub Actions workflow for a Node.js project
name: CI
on: [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: '18'
- run: npm ci
- run: npm testThis YAML configuration defines a CI pipeline that triggers on push and pull request events to the repository. It checks out the code, sets up Node.js, installs dependencies with npm ci, and runs tests. The pipeline provides fast feedback on the health of each commit.
Quick Revision
- Continuous Integration involves frequent code merging with automated build and test verification.
- It originated from Extreme Programming and aims to detect integration errors early.
- A shared version control system and a culture of collective ownership are essential.
- CI tools automate the pipeline and provide rapid feedback to developers.