Hi
This sounds like a feature that should be available after the 1.4.3 release, The good news is : we have the code the bad news is : it is in a separate trunc, which I am merging piece by piece There is so much new functionality in this branch, that we must merge it functionality wise so other devs also understand and can support it. If you would like to take a look, check the security branch https://ccnet.svn.sourceforge.net/svnroot/ccnet/branches/security and the blog of its creator : http://csut017.wordpress.com/ with kind regards Ruben Willems On Tue, Mar 3, 2009 at 11:09 AM, Adrian <[email protected]>wrote: > > This is exactly the sort of thing I'm interested in too. I would like > to approve changes before they're merged into a "final build". At the > moment, CruiseControl essentially gives me the current development > build all of the time. > > Here's my situation: > - I have a 2 month development cycle - about every 2 months I do a > full release of all my systems. > - Every day, developers check-in new features, which are built and > deployed to our dev system (using CruiseControl) for testing. > - Towards the end of the cycle, a code freeze is done - only bug > fixes are allowed in. > - We test deployment to our staging server after testing and bug > fixing is complete. > - We release. > > The problem is, that every now and again, a really urgent bug fix or > feature request comes in. In this case, I have to abandon > CruiseControl and create a manual patch, but if there were multiple > branches in CruiseControl, e.g. dev, testing and release - I could use > CruiseControl to manage deployment of patches. I could create a > process to promote checkins (features) from dev, to testing to release > and always have a trusted build in CruiseControl.
