It's not currently supported, but we'll consider doing it through the API or CLI at some point.

Each rule separately checks that all of its conditions are met before deleting a package. If any of the rules decide to delete a package, the package is deleted.

It's still on our roadmap, but it was pushed back to 4.7.

Great! Thank you for the quick response, and also for an excellent lead time. Impressive!

The feed clean-up writes logs to the database before starting, so if you have no space left on disk, then you can't start a clean-up job.

We don't have that as a retention policy currently, but can consider adding it in the future!

Note: we have now scheduled this feature for v3.6

Ok thanks for the Info

NOTE : BuildMaster has Retention Policies which are strongly recommended, rather than manually purging data That being said, you can use the same strategy to delete from that table that you used for log entries: BuildMaster 4.2 and earlier: SELECT TOP 100 * FROM BuildExecution_PlanActionVariableValues --DELETE BuildExecution_PlanActionVariableValues WHERE BuildExecution_PlanAction_Id IN (SELECT BuildExecution_PlanAction_Id FROM BuildExecution_PlanActions BEPA INNER JOIN BuildExecutions BE ON BE.Execution_Id = BEPA.Execution_Id INNER JOIN Builds B ON BE.Application_Id = B.Application_Id AND BE.Release_Number = B.Release_Number AND BE.Build_Number = B.Build_Number WHERE B.BuildStatus_Name = 'Rejected') BuildMaster 4.3 through 4.9: SELECT TOP 100 * FROM BuildExecution_ActionGroupActionVariableValues --DELETE BuildExecution_ActionGroupActionVariableValues WHERE BuildExecution_ActionGroupAction_Id IN (SELECT BuildExecution_ActionGroupAction_Id FROM BuildExecution_ActionGroupActions BEAGA INNER JOIN BuildExecution_DeploymentPlans BDP ON BEAGA.BuildExecution_DeploymentPlan_Id = BDP.BuildExecution_DeploymentPlan_Id INNER JOIN BuildExecutions BE ON BE.Execution_Id = BDP.Execution_Id INNER JOIN Builds B ON BE.Application_Id = B.Application_Id AND BE.Release_Number = B.Release_Number AND BE.Build_Number = B.Build_Number WHERE B.BuildStatus_Name = 'Rejected')

Thanks Tod, I have run your query and it deleted most of the rows out of the log table. However, Buildmaster is still timing out due to slow database performance. Are there any other tables we can reduce in size. Also we are looking to upgrade to SQL Server as soon as possible.