Continuous Integration: That’s Not What They Meant • Clare Sudbery • GOTO 2023

Whole. report TBD (trunk based development) Why continuous integration without TBD is not continuous) The main idea is that if the work is carried out in separate long-lived brunches, then the code from different branches is not integrated continuously, but only occasionally, which contradicts CI logic. Although now CI is usually referred to simply as Pipelines, which run to assemble code from individual brunches. TBD, on the other hand, is (website trunkbaseddevelopment.com)

A source-control branching model, where developers collaborate on code in a single branch called ‘trunk’ *, resist any pressure to create other long-lived development branches by employing documented techniques. They therefore avoid merge hell, do not break the build, and live happily ever after. Clare's entire report goes on to detail TBD and CI/CD, and quotes prominent engineers and consultants on the subject:)

It’s funny that this report develops the topic of DevOps and CI/CD, which were touched upon in this article. yesterday's post Code of Leadership, "Prject Phoenix" (Project Phoenix.)which we discussed with Vanya Mikheev.

#Devops #Software #Processes #Engineering