Re: Adding a build for a branch
Greg Akins <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
On Fri, May 8, 2009 at 8:51 AM, Chuck Burgess <[email protected]> wrote: > 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. > -- Thanks Chuck So do you mean that you keep "everything" in the CC build separate (artifacts, logs, checkout directories) or do you just mean that you move the branch dir structure out.. I'm thinking of the suggested dir structure for Subversion where I'd have a project dir and directories for branches project - trunk - tags - branches But it sounds like you're suggesting something more like (by they way, the top level of my CVS project is "java" which is kinda lame, but was named a long time ago...) ccWork - checkout - java <- HEAD - branches - java <- BRANCH I guess my biggest concern is "mixing" artifacts from the two builds... -- Greg Akins http://www.pghcodingdojo.org http://pittjug.dev.java.net ------------------------------------------------------------------------------ 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