|
|
|
[
Permlink
| « Hide
]
Robin Shen [21/Sep/16 12:32 AM]
This sounds more like your build script issue instead of QB issue, please check your build environment.
I did some environmental issue and it looks just fine.
Do you have any tips to find out what is happening in such cases? Any debugging methods or some verbose flag for step? You may turn on debug logging to have QB print the command being executed, and then run that command from command line directly under the same working directory with same OS user to see if the problem is the same.
Do you mean turning this logs on QB server or on the agents? Which level would you suggest DEBUG, TRACE, ALL? Current log level is set up to INFO on QB server and agents.
Currently our QB server logs are ~500MB daily, how would it increase if we change it to lower level? I mean the build log level which can be specified in general setting of the configuration.
|