forums.parabuildci.org

I have automatic build jobs that run throughout the day, and I have nightly jobs that run once per evening. If my automatic job fails, the system enforces the nightly to use an auto as a build reference so I will not get an attempt to build my latest change list, rather, the nightly job will grab th...

$ du -hs /opt/parabuild/etc/* 13M /opt/parabuild/etc/app 4.0K /opt/parabuild/etc/build 52K /opt/parabuild/etc/conf 502M /opt/parabuild/etc/data 180M /opt/parabuild/etc/index 5.4G /opt/parabuild/etc/logs 2.1M /opt/parabuild/etc/msgs 8.0K /opt/parabuild/etc/system 247M /opt/parabuild/etc/temp 28M /opt...

$ du -h -s /opt/parabuild 4.7G /opt/parabuild $ du -h -s /opt/parabuild/* 3.4M /opt/parabuild/bin 2.2M /opt/parabuild/docs 4.6G /opt/parabuild/etc 85M /opt/parabuild/jre 9.8M /opt/parabuild/lib 248K /opt/parabuild/license 51M /opt/parabuild/logs 128K /opt/parabuild/Parabuild.wsdl 12K /opt/parabuild/...

Checked in more detail (I was off by a factor of two): parabuild.data 378597064 bytes (362 Mb) [not 3 Gb as earlier reported] Still same underlying problem, although I'm now seeing evidence in the error logs in the form of INFO messages that some amount of history is being purged. Drive use has incr...

I have a restriction on the amount of disk space I have for the Parabuild control server, and no need for more than 31 days of storage, build history or logging of any kind. I've noticed my HSQL database has hit 3Gb and is likely far larger than required. I perform no builds on the build host, inste...