3 ms·
It depends on the use case. The author specifically says it is a workflow for /continuous delivery/. We do continuous delivery and our branches typically live
by benjiweber 13y ago
It depends on the use case. The author specifically says it is a workflow for /continuous delivery/.
We do continuous delivery and our branches typically live for about an hour before they are pushed to production.
Continuous delivery is about working in small deployable steps and using techniques that allow you to release incomplete features into a production environment (Feature toggles, Branch by Abstraction).
Feature branches are pretty much the opposite of continuous integration. By definition your changes are not integrated into production or with other people using other branches
http://martinfowler.com/tags/continuous%20integration.html http://martinfowler.com/tags/continuous%20integration.html
- shaggyfrog 13y agoFeature branches really have nothing to do with CI per se. A feature branch is to test major changes without upsetting the stability of your build. Depending on your code review process, it also gives people a chance to give feedback and make changes before everything's merged back into develop. In fact, the TeamCity CI system now supports automatically building feature branches -- so the two concepts are definitely not at odds.