Re: Adding a build for a branch
Chuck Burgess <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
On Fri, May 8, 2009 at 7:47 AM, Greg Akins <[email protected]> wrote: > Wondering what the best practice might be for adding a "Branch" build. > > I'm using CVS and don't have a "branch" directory in source control. > > As such, I'm tempted to add a separate CruiseControl project with the > branch directory checked out to a completely different hierarchy. > > ccWork > - checkout > - java <- HEAD > - branch <- my BRANCH > > Is it this straight-forward, or am I missing something? > > > -- > Greg Akins > > http://www.pghcodingdojo.org > http://pittjug.dev.java.net > I keep my tracked branches completely separate from HEAD, as they represent completely unrelated *builds* in my mind. The HEAD mainline of one code project stands alone, and any branches of that code project also stand alone, from CC's perspective. -- CRB ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Cruisecontrol-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user