Jon is a self-taught programmer, started in video games but now does web development. He follows principles, argues for scientific software development, and does not like writing in the 3rd person.
Code is committed by an engineer in a feature branch
It specially recommends trunk based development: short lived (less than a day) branches only, no feature branches.
It also does not suggest CI-per-branch (I don’t think their research covers if it’s explicitly a positive or negative) but it does specifically recommend trunk-based-CI.
Very good point Jon. They indeed focus on Short lived branches and there are no mentions to CI-per-branch on the research.
I tried to bring some of my experience to the post where I have worked in different companies and have seen very successful projects with amazing speed like deploying to production several times a day using the style I mentioned, which I think is absolutely fine, specially if you are taking incremental steps towards CI/CD.
Trunk based development has its own gotchas that could be tricky to adopt if you don't have a reliable CI/CD pipeline in place already. But I absolutely see its value.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It’s a great book!
It specially recommends trunk based development: short lived (less than a day) branches only, no feature branches.
It also does not suggest CI-per-branch (I don’t think their research covers if it’s explicitly a positive or negative) but it does specifically recommend trunk-based-CI.
Very good point Jon. They indeed focus on Short lived branches and there are no mentions to CI-per-branch on the research.
I tried to bring some of my experience to the post where I have worked in different companies and have seen very successful projects with amazing speed like deploying to production several times a day using the style I mentioned, which I think is absolutely fine, specially if you are taking incremental steps towards CI/CD.
Trunk based development has its own gotchas that could be tricky to adopt if you don't have a reliable CI/CD pipeline in place already. But I absolutely see its value.