we have noticed, that for directory “ci_ws\ws” clean up does miss some sub-directories. It appears, that Continua does cleanup by checking existing projects/configurations. However, if they get deleted, the cleanup misses to remove the build artifacts. This is just an assumption. Whatever… imo the folder should be checked by age of builds, so that all out-dated builds get deleted. This has lead to blocking disk usage of our buildserver. We deleted them manually, now.
When the cleanup runs it iterates all configurations including deleted/archived configurations. If a configuration has been marked as archived in the database, it cleans up all builds (workspace and database) associated with that configuration. Otherwise, only out-dated builds get deleted according to the cleanup policy.
If you can see a case which does not fit these rules, then we would be interested in finding out more. Does the build exist in the database with an id the same as the folder? Is its configuration marked as archived in the database? What is the build policy for the configuration? We can provide the SQL statements to help diagnose a cleanup problem if required.
How do i archive a configuration?
Thanks for your feedback. The builds which do not get deleted, exist in the agent workspace. We have configured the agent cleanup policy to not delete failed builds (for debugging purposes). Do failed agent builds ever get deleted?
When you “delete” a configuration, it is not actually deleted from the database but row is marked as archived. That’s just an implementation detail really.
The agent build workspace should get cleaned up when the server build workspace gets cleaned up (due to the Server Cleanup Policy).
Thanks for your help Dave. I’ll have an eye on it and let you know, if i have relevant information.