We have limited space on our QB3 server where the storage directory is that stores build artifacts and build logs. I would like to keep all of this storage stuff for all time but don't want to have to worry about running out of disk space on our server. If I point the storage directory to a network share, I worry about the performance of the builds by adding more network traffic writing log entries to the network share. How about allowing me to configure multiple storage directories in the web interface. I would setup the local drive as the primary location where all active builds use for speed. I could then setup a network share with a much larger hard drive as a long term storage directory. Then I could move build storage directories from the local to the secondary storage location and QB3 server could still find them. It would know to first look in the primary and then look in the secondary. As a bonus, it would be great if the build retention mechanism could be used to automatically move builds older than a certain age from the primary storage dir to the secondary storage dir.
|
