🎁 New User? Get 20% off your first purchase with code NEWUSER20 · ⚡ Instant download · 🔒 Secure checkout Register Now →
Menu

Categories

DevOps Intermediate

What is Trunk-Based Development?

A source control strategy where developers integrate small changes directly into the main branch frequently, often multiple times per day.

Trunk-based development minimizes merge conflicts and enables continuous integration by having all developers commit to a single shared branch (trunk/main). Short-lived feature branches (lasting hours, not days) are permitted but must merge quickly. This approach requires strong automated testing, feature flags for incomplete work, and code review practices. It enables continuous deployment since the trunk is always in a deployable state. Google, Facebook, and other tech giants practice trunk-based development at massive scale. It contrasts with GitFlow where long-lived branches can diverge significantly.

Related Terms

Configuration Management
The practice of systematically managing and maintaining consistent server configurations across infrastructure.
Environment Variable
A dynamic value stored outside the application code that configures behavior without hardcoding sensitive or environment-specific data.
Istio
An open-source service mesh that provides traffic management, security, and observability for microservices on Kubernetes.
Blue-Green Deployment
A deployment strategy using two identical environments where traffic is switched from the old version to the new one instantly.
Artifact Repository
A centralized storage system for build artifacts like compiled binaries, packages, and container images used in CI/CD pipelines.
SonarQube
A platform for continuous code quality inspection that detects bugs, vulnerabilities, and code smells through static analysis.
 View All DevOps Terms →