The by-products of builds (like artifacts and logs) can over time use Every build that is executed within Continua stores additional information in the server's workspace, such as artifacts and build logs. These by-products are vital for tracking build information, however they can also take up considerable disk space over time. Cleanup policies provide a way to remove any unneeded or old build data to reduce the disk space Continua is using.
The By default, the global policy will by default be applied to all builds, but however you can override this at either the the project or configuration level level. Each cleanup policy runs once per day. You can choose when it runs , as well as and control which builds and by-products are cleaned up.
NB: build Note that build cleanup is permanent: a cleaned up build cannot be recovered.
...
The global cleanup policy can be modified in the administration section under 'Cleanup'.
There are several options you can change to determine which builds will be cleaned up:
Build Age: Build that finished more than 'Any build that is older then the build age ' ago will be cleaned upremoved.
Minimum Builds: Regardless of build age, this number of builds will always be kept.
...
Database: The build is deleted from the Continua database - it no longer appears on the configuration's History page, nor does it contribute to the configuration's stats.
Save: saves Saves the cleanup policy. It will be executed according to schedule
Save and Run Now: saves Saves the cleanup policy and runs it the cleanup immediately.