Continuous integration with multiple branch development
        Posted  
        
            by ryanprayogo
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by ryanprayogo
        
        
        
        Published on 2010-04-23T20:01:19Z
        Indexed on 
            2010/04/23
            20:03 UTC
        
        
        Read the original article
        Hit count: 265
        
In the project that I'm working on, we are using SVN with 'Stable Trunk' strategy. What that means is that for each bug that is found, QA opens a bug ticket and assigns it to a developer. Then, a developer fixes that bug and checks it in a branch (off trunk, let's call this the bug branch) and that branch will only contain fixes for that particular bug ticket
When we decided to do a release, for each bug fixes that we want to release to the customer, a developer will merge all the fixes from several bug branch to trunk and proceed with the normal QA cycle.
The problem is that we use trunk as the codebase for our CI job (Hudson, specifically), and therefore, for all commits to the bug branch, it will miss the daily build until it gets merged to trunk when we decided to release the new version of the software. Obviously, that defeats the purpose of having CI.
What is the proper way to fix this issue?
© Stack Overflow or respective owner