Re: Adding a build for a branch

On Fri, May 8, 2009 at 8:38 AM, Greg Akins <[email protected]> wrote:

> 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
>


Yes, I keep the branches entirely separate from HEAD, so that build results
and artifacts are entirely separate.  Again, in my eyes, the *builds* are
unrelated to one another, and therefore should *never* mingle.

If you were to follow that Subversion *repository organization* layout for
your CC sandboxes, it implies to me that you're making the "project" level
be your "one" CC build, as if your trunk and any/all branches would all be
built together as one big build.  I don't think this is what you're after.

Now, if your intent for the layout is instead just for organizing where you
locate your individual branch/HEAD sandboxes and you're keeping their builds
via CC all separate, then I think *that* is simply up to personal
preference.  You could locate those sandboxes any way you like, as long as
the pathing you set in CC's config.xml can find them.  I still keep all my
builds set in the root of CC's /projects dir, but I could just as easily
instead make root dirs of /projects/myProject1, /projects/myProject2, and
each of those have /trunk and /branches subdirectories inside them.  In this
case, each build I configure in CC's config.xml just has to point to
/projects/myProject1/trunk/build.xml,
/myProject1/branches/branchOne/build.xml,
/projects/myProject1/branches/branchTwo/build.xml, etc.
-- 
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