Viewing logs of running builds
5 answers
There is no simple way to view the live build log using an RTC client.
The best your build can do is make finer-grained status/logs/downloads
available by using the build toolkit ant tasks to publish the info as its
available. See the log and artifact publishers, as well as the
startBuildActivity task. This is the recommended way to show somewhat live
build progress in the RTC client.
One crazy idea, if you were willing to run tomcat or similar on your build
machine and dump your log to a directory visible via http.... Then, you
could publish a link to this area with the linkPublisher. Then, users could
view this (assumingly live updated) log by browsing to that web page from
the build result in RTC.
The best your build can do is make finer-grained status/logs/downloads
available by using the build toolkit ant tasks to publish the info as its
available. See the log and artifact publishers, as well as the
startBuildActivity task. This is the recommended way to show somewhat live
build progress in the RTC client.
One crazy idea, if you were willing to run tomcat or similar on your build
machine and dump your log to a directory visible via http.... Then, you
could publish a link to this area with the linkPublisher. Then, users could
view this (assumingly live updated) log by browsing to that web page from
the build result in RTC.
Ryan, what I would really like to do is very similar to that suggested in your last post. We have a custom Ant logger that dumps log data in near real time to our build website. My concern is, I don't think I want to override the log file being kept by Jazz. How is Ant being called under the covers? Can I safely put -logger on the Ant command line in the build definition and still have Jazz get a copy of the build console? I actually prefer the output from our logger. It adds timestamps to every line.
The "full build log" that you see in the RTC build result is simply the
stdout and stderr captured by the jazz build engine when it invoked ant for
you.
The invocation of ant is straightforward and its given the ant arguments
specified in the build definition. So, RTC should not be getting in the way
if you want to specify a different logger.
stdout and stderr captured by the jazz build engine when it invoked ant for
you.
The invocation of ant is straightforward and its given the ant arguments
specified in the build definition. So, RTC should not be getting in the way
if you want to specify a different logger.