Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for cleaning up older integrations? #269

Closed
reststop opened this issue May 14, 2016 · 2 comments
Closed

Support for cleaning up older integrations? #269

reststop opened this issue May 14, 2016 · 2 comments

Comments

@reststop
Copy link

reststop commented May 14, 2016

Question: Is there any support for cleaning out old integrations?

For example, setting a limit, either by date (how old), or by the number of current integrations available on disk, or clearing the cache for a particular bot.

Yes, this isn't specifically for Syncer/PR bots in general, since they are automatically created, and deleted. Do we know if the Integration cache is deleted for an integration, or for the bot when it is deleted?

One of our projects is very large (on the order of nearly 2 GB in source and frameworks in git) and each IPA created (15 of them for every Integration) close to 250 MB each (8.75GB), and growing. Currently I manually remove older integrations, via the server GUI or simply deleting the IntegrationAssets directories for older integrations (which leaves the integrations in the servers database).

This might not be germane to Buildasaur, and might be a separate project using the server SDK, but I thought you would one of the best people to ask if you know if any working projects, or projects in progress on this topic.

Thanks.

@czechboy0
Copy link
Member

All that is in Xcode Server's responsibility, unfortunately Buildasaur can't affect that AFAIK.

@reststop
Copy link
Author

Thanks. I'll have to take a look deeper into a new project. Actual space
can be done with some simple scripting, but cleaning up the DB is the hard
part. I cannot believe that Apple didn't think to add that capability.

On Sun, May 15, 2016 at 10:51 AM, Honza Dvorsky [email protected]
wrote:

Closed #269 #269.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#269 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants