https://citconf.com/wiki/index.php?action=history&feed=atom&title=Can_Feature_Branching_Work_with_CI 2026-04-25T05:18:25Z Revision history for this page on the wiki MediaWiki 1.35.11 https://citconf.com/wiki/index.php?title=Can_Feature_Branching_Work_with_CI&diff=5740&oldid=prev 2008-04-10T07:56:27Z

<p>Move Kevin&#039;s comments from his page to here</p> <p><b>New page</b></p><div>Topic proposed by [[Kevin Dietz]]:<br /> <br /> For those who missed my talk on feature branches in a continuous integration environment, the consensus seemed to be that you shouldn&#039;t do branches unless absolutely necessary because it adds a lot of overhead that isn&#039;t worth the benefits in most cases. I&#039;m still curious about the concept of feature branches, however, and I&#039;m wondering if there are ways to improve the current state of the art so that feature branches can exist more peacefully in a continuous integration environment. It could be that my interest in feature branches stems from the phase Timpani Software is in right now with the development of BuildBeat. I&#039;ve got a lot of major changes I&#039;d like to work on independently. I don&#039;t know how long each feature will take, and some of them are a bit experimental and may be abandoned if they don&#039;t work out. I just don&#039;t want to mix all this stuff up into an unstable trunk. Also, since my team is small, I&#039;m not too concerned about the problems with merging and merge conflicts caused by branching.</div>

Jtf