Hi guys,
is there a way to get a finer logging configuration? We are experiencing repository syncs that take more than a hour to finish. During the last step of the sync (saving changesets) there are lots of database locks that block the use of the CI server entirely (e.g. start build, clean up tasks run into database timeouts).
Checking the log files for the output of the sync process is quite annoying as the log gets spammed with the results of the agent properties checks and other messages. Is there a way to limit the logging output to the sync of a single repository? Our build environment has about 10 agents and 5 repositories and the server log is at about 200 MB per day.
Kind regards
Kay Zumbusch
Hi Kay,
Currently logging is very course, and there is not many options to break this down. It is a long term goal to improve the logging to include features such as categories and finer grain logging levels.