Re: cruise control log directory

Looking again, why aren't you creating a template for the project that
uses your preconfigured log?

<plugin name="project">
  <log />
</plugin>

I expect that you'd need that or have trouble everywhere.  Saying that
you were only have a problem in one project is still throwing me
off...

Jtf

-- 
 Free hour of CI consulting: http://the.ci-guys.com


On Sat, Feb 7, 2009 at 1:42 AM, Jeffrey Fredrick
<[email protected]> wrote:
>> ... However, I came across a problem that is just
>> a single ant call that don't seem to put the logs in the same place ... that
>> is unless I add the log element to the project file (see attached examples).
>
> This doesn't make any sense to me... I don't think the <ant ../>
> elements have anything to do with the <log> element so I can't imagine
> how putting the <log../> in the included project would make any
> difference at all.
>
> I'm left to ask:  are you sure?  :)
>
> I'm mostly surprised that adding the <log /> would help fix the problem.
>
> Jtf
>
> --
>  Free hour of CI consulting: http://the.ci-guys.com
>
>
> On Mon, Feb 2, 2009 at 7:50 AM, Michael Delaney <[email protected]> wrote:
>> All,
>>
>> I'm currently moving our cruise control system from Windows to Solais, and
>> with this change comes a structural change as well. Everything use to run
>> out of a single directory (c:/cruisecontrol-v2.7.3, or like naming schema)
>> however ... with the switch to Solaris we now need to move stuff around.
>>
>> With the new layout, our logs are being stored in /var/log/cruisecontrol. In
>> our config.xml, I've defined the log plug-in to point to the afore mentioned
>> location. This works in most places; as I also set the location for
>> composite/distributed builds. However, I came across a problem that is just
>> a single ant call that don't seem to put the logs in the same place ... that
>> is unless I add the log element to the project file (see attached examples).
>>
>> My question is: Is there a way to avoid having to include a null/empty node
>> definition in the xml file that I'm just over looking.
>>
>

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com