|
#1
|
|||
|
|||
How to propagate loglevel to child bld files?
Hi,
I would like to limit the amount of information / logs produced by my bld script to the console. I use Jenkins, so i would very much like to achieve a much smaller blueprint of logs. This is the command line i use for my continuous integration build: Code:
VisBuildcmd.exe Build.bld /loglevel vbldLogLevelError Now, when i have a child bld script that i call within Build.bld, /loglevel information is not propagated to that executing process, so i get a vbldLogLevelNormal verbosity from the child bld. How can i propagate /loglevel being parsed from the parent bld script, to child scripts? Thank you. Lee |
#2
|
|||
|
|||
Pass in another macro value with the log level and use that when calling the child project, specifying the log level.
|
#3
|
|||
|
|||
Thanks. Can you also include a small snippet with VBS on how to set the loglevel in the child when received?
On how to use the following: Code:
Options.LogLevel As LogLevelEnum Please excuse my inability to pickup VBS. Thanks for the help. |
#4
|
|||
|
|||
Code:
Application.Options.LogLevel = %LEVEL_MACRO% |
#5
|
|||
|
|||
Thank you.
|
#6
|
|||
|
|||
I found an interesting observation. Please correct me if i am wrong. In the documentation, it says:
Code:
vbldLogLevelNone 0 No calls to LogMessage will be logged. vbldLogLevelError 1 Only error level messages will be logged. vbldLogLevelWarning 2 Only error and warning level error messages will be logged. vbldLogLevelNormal 3 Errors, warnings, and normal level error messages will be logged. vbldLogLevelDetailed 4 Errors, warnings, normal, and detailed error messages will be logged. vbldLogLevelDiagnostic 5 Errors, warnings, normal, detailed, and diagnostic error messages will be logged. vbldLogLevelNone starts at -1, vbldLogLevelError at 0 and so on. I tested this with: Code:
Builder.LogMessage2 "vbldLogLevelError = " & vbldLogLevelError, vbldLogLevelError |
|
|