Wat is trunk-based development en hoe ondersteunt het CI/CD?

Question

Accepted Answer

**Trunk-based development** is een branching-strategie waarbij ontwikkelaars kleine wijzigingen **frequent integreren in een enkele hoofdbranch (trunk)**, met behulp van zeer korte-levensduur branches (of direct committen). Het is sterk geassocieerd met high-performing CI/CD omdat het continue integratie maximaliseert.

## Wat trunk-based development is

```text
Developers commit small, frequent changes to a SINGLE shared branch (trunk/main):
  → very SHORT-LIVED branches (merged within hours or a day) — or commit directly
  → integrate continuously (multiple times a day) into trunk
  → trunk is kept always RELEASABLE (working, deployable)
→ vs long-lived feature branches that diverge for days/weeks before merging.
```

## Waarom het CI/CD goed ondersteunt

```text
✓ MAXIMIZES continuous INTEGRATION — frequent small merges = the essence of CI
  (catch integration issues immediately; tiny, easy-to-resolve conflicts)
✓ AVOIDS "merge hell" — no long-lived branches diverging → no big painful merges
✓ Small changes = lower risk, easier review, faster feedback
✓ Keeps trunk always deployable → enables continuous DELIVERY/deployment
→ Research (DORA) links trunk-based development to high delivery performance.
```

## Omgaan met onvolledig werk

```text
How to commit to trunk frequently when features aren't done?
  ✓ FEATURE FLAGS → merge incomplete features hidden behind off flags (don't break trunk)
  ✓ Break work into small, independently-mergeable, non-breaking pieces
  ✓ Branch by ABSTRACTION → introduce changes incrementally behind abstractions
→ The discipline: integrate small, keep trunk working, hide incomplete work.
```

## Trunk-based versus feature-branch (Git Flow)

```text
TRUNK-BASED → short-lived branches, frequent integration, continuous delivery,
  feature flags — favored for high-velocity CI/CD
GIT FLOW (long-lived branches) → more structured, release-oriented, but longer
  divergence and bigger merges → less continuous
→ Trunk-based is generally preferred for true CI/CD; Git Flow for scheduled releases.
```

## Waarom het belangrijk is

Trunk-based development begrijpen is waardevol kennis op senior-niveau omdat het **sterk geassocieerd is met high-performing CI/CD** en een belangrijk branching-filosofie vertegenwoordigt, dus het is nuttig voor het begrijpen van effectieve delivery-praktijken.

Het kernidee — ontwikkelaars integreren **kleine wijzigingen frequent in een enkele trunk** met behulp van zeer korte-levensduur branches (in plaats van lange-levensduur feature branches die dagen of weken divergeren) — **maximaliseert continue integratie direct**, wat de essentie van CI is: frequent kleine merges vangen integratieproblema's onmiddellijk op en produceren kleine, gemakkelijk op te lossen conflicten, **vermijdend de "merge hell"** van lang-divergente branches.
\