I’m currently inspecting the disk space of our build server and i found many builds where we already deleted the configuration but the files are still there.
Didn’t you implemented/fixed something in the past that should deleted these orphaned files?
Some folders (ids) can be still be opened using http://server/project/ci/builds/view/2906 showing up the build page. when i click on the configuration name, i get the error page, which is correct because we deleted it.
All the other folders are still there but not cannot be accessed using the site using any known link.
Hi Christian,
Thanks for reporting this. I’ve looked through the code and there is a place where we are excluding archived configurations from the build cleanup. We’ll get a fix out in the next release.
that orphaned ones seemed to be gone. gained 4GB of space back. but there are still some builds that should have a cleaned up workspace.
My policy for testing is:
Age: 3 Days
Minimum: 3 Builds
Maximum: 5 Builds
Cleanup: all but Database
Now i have many builds (at least 50+) that still have files in the workspace from different configurations (that still exist). i do not have overridden any cleanup policy nor is any of these builds pinned.
So maybe i misunderstood something or something is not working as intended
Hi Christian, thank you for getting back to us. We will need some further information in order to troubleshoot this one further.
- Are any of these builds pending promotion? (we cannot cleanup these ones due to the possibility of a later promotion). If this is the case you can enable the setting ‘enable stage promotion timeout’ within the associated stages (note that this will only take effect on builds going forward), or stop the build, which will allow the builds to again be eligible for cleanup)
If the above is not the case we will need more detailed diagnostics;
- Please send us a debug log for a cleanup run (http://wiki.finalbuilder.com/display/continua/Debug+Logging), go into one of the configurations that is not being cleaned up and select the “save and run cleanup now”. Please also generate a diagnostics report (http://SERVERNAME/administration/events) and select diagnostics report from the top box.
Please send these details to support@finalbuilder.com and we can look closer.
hm ok, sounds pretty simple. the promotion ist our last stage called deploy and for all those old builds this option was not available.
Now i set it to 72 hours but i assume that those all builds will not be changed, so this only applies to new builds?
If so, how to “stop” all those all builds?
Hi Christian,
Yes - this will only apply to new builds. Currently you have to click the Stop button for each build. We need to add a Stop All button which will also allow you to optionally stop all but the latest build awaiting promotion. This is now on our to-do list.
ok, i won’t stop all those 5000+ builds * …
Hi Christian,
It’s safe to delete any for old build folders manually if you no longer need to promote or view the log file. I’ve set the priority high for the Stop all Builds button task.
is there any concrete schedule for the “Stop all previous builds” button or do i need to extend our virtual build server harddisk?
If you are considering functionality to “Stop All Builds”, can you also consider adding the functionality to “Stop all builds within one or multiple Projects”? Thanks
This feature should be available soon, the team is currently merging & testing a bunch of changes, preparing for a release. Stop all builds will be a per configuration feature only. There is also the “Enable Stage promotion timeout” feature on stages in the current release, if you are not already using it I recommend adding it to your manual promote stages.
Die “Stop all builds” button ran into an client side timeout but the server has stopped all (6500) correctly. Now i got 50GB of space back thank you.
Hi Christian that’s great news Happy to hear that this is all sorted now.