Re: multiple projects with *one* source tree

Niklas Nylund <[email protected]>
Newsgroups gmane.comp.java.cruise-control.user
Message-ID <[email protected]>
Hi,

I am running a setup where the same SVN trunk is checked out multiple times to different local working copies and they each have one or more CruiseControl builds associated with them. This works in my experience as long as CruiseControl only uses one thread (i.e. only one build active at a time).


Niklas

On 20 jan 2010, at 21.44, Tennis Smith wrote:

> Hi,
> 
> I have 2 projects that use the same source env.  The only diff is that one proj runs tests that take hours instead of minutes.  I was thinking that I could have a single source tree for both, and only have the build.xml files (etc) in the project dir.
> 
> Will that work?  Do people often share source trees in CC among multiple projects? (Yes, I'm a CC n00b).
> 
> -- 
> 
> Tks,
> -T
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev_______________________________________________
> Cruisecontrol-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user


------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.