Best RedGate CI process with parallel development
rhsu
Posts: 10
We use RedGate Source Control and Schema compare (command line interface) in our database CI process for DDL changes. In our company, there are always parallel releases going on and we are able to create branches with svn and still use RG source control with no problem. And when two releases need to be test in the same QA environment at the same time, we have to merge the first branch into the second branch so the changes in first branch would not be overwritten when deploying the second branch. However, the branches have different release schedule and it is possible that the second branch needs to be released before the first branch. Things become complicated when this happens, we have to "un-migrate" branch 1 from branch 2. It is error prone and it is really not a good "CI" process. I am wondering if anyone have the same issue and what is the best way to deal with parallel releases with Red Gate?
Thanks
Roger
Thanks
Roger
Comments
In the next version of the tool there's going to be the facility to only deploy certain change types from the command line so you could deploy both branches to the same database. If your two branches have filters that are mutually exclusive that will also be supported by the command line.
I'm honestly not sure what to suggest.
Project Manager
Red Gate Software Ltd
http://documentation.red-gate.com/displ ... ng+objects
I plan to back-port this to the other tools as soon as I get some time, hopefully early next year.
Project Manager
Red Gate Software Ltd