Trunk Based Development

Smaller Teams:

  • Small commits straight into the trunk(or master)
  • 이 방식은 Pair Programming 방식을 취한다. Pull Request 방식의 Code Review 불가능.

Scaled Trunk-Based Development:

With trunk-based development, where developers merge small, frequent updates to a core “trunk”

  • Committing changes to the master branch triggers the CI/CD pipeline.
  • If the pipeline flags up any failures, it is everyone’s responsibility to jump in to try and fix it as soon as possible.
  • The aim is to keep the master branch in a deployable state, with changes being released frequently.

Long-Lived Feature Branch

Feature Flags & Branch by Abstraction 은 Long-Lived Feature Branch 를 위한 기술이다.

Perceived Barriers to Trunk Based Development

Perceived Barriers to Trunk Based Development