๐ŸŽ 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

Prometheus
An open-source monitoring and alerting toolkit that collects time-series metrics using a pull-based model.
Chaos Engineering
The discipline of deliberately introducing failures into a system to test its resilience and identify weaknesses before they cause outages.
Semantic Versioning
A versioning scheme using MAJOR.MINOR.PATCH numbers that communicates the nature of changes in each release.
GitFlow
A branching model for Git that defines a strict workflow with feature, develop, release, hotfix, and main branches.
Ansible
An agentless automation tool for configuration management, application deployment, and task automation using YAML playbooks.
Rolling Update
A deployment strategy that gradually replaces old application instances with new ones, maintaining availability throughout.
View All DevOps Terms โ†’