Continuous integration

lastmod 2026-08-03created 2015-05-1850 edits

In software engineering, continuous integration (CI) is the practice of running a process that continuously applies quality control (Quality Control) - small units of work, applied frequently. Continuous integration replaces the classical approach of applying quality control only after all development is finished, and focuses on improving software quality and reducing the time it takes to release software. A representative CI tool is Jenkins.

Categories

• Continuous integration (CI)
• ContinuousIntegration:ImplementationGuide - CI/CD Platform Implementation Guide
• Continuous build (CB)
• Continuous delivery (CD)
• Continuous deployment (CD)
• Continuous Testing (CT)
• Infrastructure as Code (IaC)
• Hudson
• Jenkins
• Bazel (Korean: 바젤)
• CruiseControl (Korean: 크루즈 컨트롤)
• Github Actions
• Gitlab CI
• Drone
  • Woodpecker CI - A modified fork of Drone 0.8, made after Drone switched from Apache 2 to a proprietary license
• Travis CI
• Dagger
• CircleCI
• Bamboo (Atlassian)
• Argo CD (GitOps; k8s)
• Tekton - Kubernetes-native CI/CD framework
• Flux CD
• Buildkite
• Concourse CI
• Spinnaker
• Openship - Self-hosted deployment platform with built-in CI/CD

API

• Poozle - Open-source single API for service integrations

ETC

• Wait4X - Lightweight tool that waits until services are ready
• Komodo - Tool for building/deploying across multiple servers

Pipeline

1. Code
2. Commit
3. WebHook
4. Build
5. Unit test
6. Integration tests
7. Review
8. Staging
9. Production

Favorite site

• How does Facebook develop and deploy? ¹

Docker

• Building Docker images with Jenkins
• Automating builds and tests with Docker and Gitlab CI
• Automatically build and push Docker images using GitLab CI

References