Re: Multiple instances of CC
Andreas Gundermann <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
We use multiple instances in order to manage several projects independently of each other (one project with its branches on each instance). With a single bin we wanted to keep the discspace and costs of configuration low. We tried the antWorkingDir - it works. But we think that this not substitude the antBuilderOutput.log and it is also not the same content. At the moment we are not able to use multiple threads, because there are dependencies between CC-projects on a single CC-instance. But we will try to reorganize our Builds so that we are able to use multiple threads. My main question remains whether CC is at all suitable for being used in different instances. OR: Is there any reason not to create multiple instances on one binary? The other not answered question is: Is there any way to configure the log dir for "Build Results JSP". Andreas Am 19.02.2011 18:47, schrieb Dan Rollo: > Hi Andreas, > > I haven't heard to using the same CC bin w/ multiple instances before. > May I ask why you are doing that? > Is using multiple threads in a single instance viable? > http://cruisecontrol.sourceforge.net/main/configxml.html#threads > > Due to the way AntOutputLogger currently works to read the live build > output from ant via an ant listener, the output is hardcoded to be > written to a specific filename. It's possible, but would be tricky, to > change that to allow some way to use a different file name. > > Another workaround might be using different antWorkingDir's for any > projects that might build concurrently. The ant builder live output file > is created in the antWorkingDir. > > Still, using the first suggested approach of multiple threads will > ensure that a given project is never built twice at the same time, but > will allow multiple different projects to build at the same time. > > Hope this helps. > > Dan > > >> Date: Fri, 18 Feb 2011 10:54:02 +0100 >> From: Andreas Gundermann<[email protected]> >> Subject: [Cruisecontrol-user] Multiple instances of CC >> To:[email protected] >> Message-ID:<[email protected]> >> Content-Type: text/plain; charset=ISO-8859-15; format=flowed >> >> Hi, >> >> we are using multiple instances of CruiseControl based on the same bin. >> At the moment all works fine. We are using the Dashbord to check and >> force the builds. Just the little problem we have that the instances are >> using the same antBuilderOutput.log and then a task of instance one >> waits until an other task of instance two finshed his ant call. But when >> I want to use the "Build Results JSP" there is only the parameter logDir >> I can define in web.xml for all instances. But with different >> directories for each instance, this is not enough. >> >> Therefore, I first would like to know if I can configure the fileName >> and directory of antBuilderOutput.log by instance and if I can save this >> file to a location specified beyond. >> >> I would also like to know if I'm right that there is no way to configure >> the log dir for "Build Results JSP". >> >> The last question is whether CC is at all suitable for being used in >> different instances. >> >> best regards >> Andreas > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Cruisecontrol-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d