We have reached the 4th installment of the series telling how we implement trunk-based development at Codice today. Previously, we covered:
- How we changed our working cycle to move to trunk-based development.
- The difference between releasing and deploying.
- What exactly trunk-based development is and how it blends with task branches.
Today, we will answer some common questions that were not covered before. So far, we just described the ideal cycle, but never told you what happens if tests fail, the various reasons why a task/branch can be rejected, what to do when a branch can’t be merged or how to handle broken builds. These are the topics we cover today.