We've got an extremely busy 100-agent server, and we try not to restart it for extended periods of time if we can avoid it.
The Bamboo server process redirects all output to <BAMBOOINSTALLDIR>/logs/bamboo.log
This single log file will be populated without limit until the next time Bamboo is restarted, at which point it will be over-written completely.
There's two problems that need addressing:
- Restarting Bamboo should not wipe out the the existing logs. Right now we have to remember to copy the log before we start Bamboo so as we don't lose it.
- Bamboo is run via the Tanuki wrapper, but bamboo.sh over-rides any logging properties that are set in <BAMBOOINSTALLDIR>/conf/wrapper.conf. We really want to have great control over log roll-over, and wrapper.conf is the most appropriate method to do this. Because all logging is in a single enormous bamboo.log, it makes analysing it and sending it to Atlassian Support a major PITA if the log is a few days old. We really want to be able to roll-over daily.
Suggestion