Users incur Unity Build Automation storage charges by archiving projects without deleting build history. To stop or reduce these costs, delete the build history manually via the Build Automation dashboard by unarchiving the project, selecting all builds (or the ones targeted for deletion), deleting them, and then re-archiving the project. Deletion is irreversible, so back up build history locally beforehand.
Symptoms:
- I found unexpected charges for Build Automation storage, and I want to stop them.
- I have been charged monthly for storage, but I can't identify which Unity product is incurring the cost.
- I want to reduce the amount of storage in Build Automation.
- The storage of my project, built in Build Automation, has increased significantly.
- I want to prevent charges caused by the increase in the Build Automation storage usage.
Cause:
Many users archive their projects without deleting the build history, which can result in ongoing storage charges. To avoid these charges, it is necessary to delete the build history.
Resolution:
To reduce storage usage and manage costs linked to Unity Build Automation storage, you need to delete the build history of each project where builds have been created. Since this process must be done manually, please follow the steps below to manage this process:
| Please note that the deletion is irreversible. Back up your build history locally before you proceed with the deletion process. |
- Sign in with your DevOps credentials on the Build Automation dashboard.
- Go to the list of archived projects (in case the project was archived) and unarchive it:
- Select the specific project to manage.
- Navigate to the "Build history" page of the selected project.
- Choose "Select all" to select all builds within the build history.
- Click "Delete" and then confirm deletion to eliminate the selected builds:
- Archive the project once again after deletion.
More information: