Rethink the cache system to be more reliable

Description of the feature request

I cached GEM_HOME and then my build broke after updating dependencies. The cache should be smarter about deleting dirs based on changes (ex: Gemfile.lock, Podfile.lock) to prevent build problems.

I don’t have a great solution but it’d be nice to make sure the cache is as robust as possible and works well for common use cases (rubygems, cocoapods, etc.)

Use case / for what or how I would use it

I’d like to use the cache to improve build speeds. Not using the cache means builds are slow.

It would be awesome to have a feature to delete the cache on a schedule. API support for cache control would also be nice. Currently the cache exists forever until manually purged and that tends to create false positives.

Regularly and proactively cleaning/refreshing the cache would be nice.

Definitely a great idea @bootstraponline, thanks for the #feature-request! :slight_smile:

1 Like