Installing external dependencies on every build can take quite some time. This is why at the end of last year we introduced dependency caching. Since then, we have kept on improving the feature, most recently launching Mac support.

Clearing Caches

Sometimes your cache gets stale and contains files that will cause your build to fail. For instance, a cache may be invalidated by build environment updates if the cache contains compiled code. It might well be that the only solution is to get rid of the old cache.

[  ](http://docs.travis-ci.com/images/cli-cache.png)

To make it possible for you to get an overview over your caches and delete them if need be, we added the cache command to our command line client at launch.

New UI

We are happy to announce a new view inside our web UI. Like the command line client, it allows you to view which caches exist and clear out a single cache, all caches for one branch, or all caches all at once.

[  ](https://api.monosnap.com/image/download?id=Umct4Y3ZceLv8xw4RNqhsFDNBoRL09)

To get to the cache view, navigate to any project on Travis Pro and you should find a “Caches” link in the cog menu.

Cache fallback

Please keep in mind: If you delete the cache for a branch other than master, the next build on that branch will fall back to the master cache instead of using an empty cache. This is important if the master branch cache is causing issues, too.