Re: How to redirect output (while building) to the dashboard

I think there is some confusion about the AntBuilder specific 
'showAntOutput' tag and 'showProgress' - they are very different.

1. showProgress - sends small (light network load) messages back to the 
master CC instance.
This tag is available on all builders, and works fine for multiple CC 
threads, as well as for remote/CCDist build agents.
It does NOT include the full build output.
As far as I know, this output is not used anywhere in Dashboard, but it 
does appear in the JSP Reporting app.

2. showAntOutput - applies ONLY to the AntBuilder (and now 
Maven2Builder), and does not work well with multple CC threads, and I 
don't think it works at all for remote agents.
Logs ALL builder output to a file.
This output shows in Dashboard (but not in the JSP Reporting app).


There is a bug pending (CC-911) that attempts to fix the 'showAntOutput' 
to work better with multiple CC threads. However, related to that bug, I 
am also working on a proposal that would extend the "log output to file" 
feature to all Builders (and Bootstrapers, and Publishers). (The 
proposal would also extend the 'showProgress' [light network load] to 
Bootstrappers and  Publishers). This would allow "live output" for most 
components to be visible in Dashboard.

The proposal would break backward compatibility in that the 
Bootstrapper, and Publisher interfaces would all get a new parameter 
(Map<String, String>) that holds info like the project name, etc.

See this Jira issue for more info:
http://jira.public.thoughtworks.org/browse/CC-911

Please comment that issue if you have any suggestions/concerns/etc.

Dan


From: Chuck Burgess <[email protected]>
Subject: Re: [Cruisecontrol-user] How to redirect output (while 
building) to the dashboard
To: [email protected]

Steven Zedeck <[email protected]> wrote:
 > >
 > >
 > > Chuck Burgess-2 wrote:
 >> > >
 >> > > On Wed, Apr 7, 2010 at 9:49 AM, Steven Zedeck 
<[email protected]> wrote:
 >> > >
 >> > > I think you might be wanting *showAntOutput="true"* in your
 > > <schedule><ant
 >> > > /> tag in *config.xml*...
 >> > > --
 >> > > CRB
 >> > >
 >> > >
 > >
 > > I'm not using ANT in this particular project. I have a PERL script that
 > > does
 > > the build via the <exec> tag and I don't see any attribute that 
applies to
 > > this.
 > >
 > > thanks for all your help. I appreciate it,
 > > Steve
 > >


Ah, ok... I'd assumed *config.xml* called an ant script that itself used *
exec* to launch your perl script.  Instead, you're using scheduled->exec
directly in *config.xml*.

Judging from the docs, the *showProgress* attribute exists on both the *
schedule* and *exec* tags, but both default to *true* anyway.  That implies
to me that you'd have to explicitly set one/both to *false* in order to
silence the output from your perl script.  Also, since you see it in your
console, I'm curious as to whether or not you also see it in your *
cruisecontrol.log* file.

It may be that the dashboard webpage itself doesn't really provide a
constantly updating, in progress view of the build log during the build.
I've never tried to see that for a build in progress from the dashboard.  I
just checked on one of my CC dashboards, and I confirm that I see nothing
during the build under the Build Output tab.  However, once the build is
finished, I do see the build log available to be downloaded/viewed from the
Build Log tab.
-- CRB -------------- next part -------------- An HTML attachment was 
scrubbed... ------------------------------ 
------------------------------------------------------------------------------ 
Download Intel&#174; Parallel Studio Eval Try the new software tools for 
yourself. Speed compiling, find bugs proactively, and fine-tune 
applications for parallel performance. See why Intel Parallel Studio got 
high marks during beta. http://p.sf.net/sfu/intel-sw-dev 
------------------------------

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev