|
#1
|
|||
|
|||
How to disable steps trace in the log?
It is possible to to that for particular steps via step script but how to do that globally?
The trace is usefull during debugging but it makes logs huge. |
#2
|
|||
|
|||
To enable/disable logging on a global basis, set or clear the LOGFILE macro, either by passing it in on the command-line or by disabling logging at the start of the build in the vbld_BuildStarting event.
|
#3
|
|||
|
|||
Deer Administrator,
thank you for the prompt answer but my question is little bit different. Here is the example of the log: 9/19/2003 1:09:54 PM: Building subroutine step 'Log Parms'... 9/19/2003 1:09:54 PM: Building subroutine step 'Log Settings'... ******************************************* *** BROADbeam Automated Build Procedure *** *** Product: BDS *** Component ExpressQ log file started at 9/19/2003 1:09:54 *** Build type: Scheduled *** VSS Label: BDS.4.1.1 *** ******************************************* How to disable the 1st two lines in the log (the trace of the script commands?). It is convinient to have them during debugging but this trace makes log huge and hardly readable. It would be good to have option to limit log with only 3d party console output and explicit writes to the log. Regards, Vladimir |
#4
|
|||
|
|||
You can't disable that part of the logging for the built-in logging components. However, you could create your own custom logging component that does what you require and plug it into VisBuildPro. Lookup 'VBPLogger sample' in the help index and see that sample for more details.
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|