Caching now available for everyone

We have very exciting news to share with you today. We are bringing caching support to open source projects.

A Brief History of Caching on Travis CI

In December 2013, we introduced caching to users running on our private platform, allowing faster builds.

One year later, in December 2014, we brought caching to open source repositories running on containers.

This left open source projects running on our Mac infrastructure, and those running on legacy and the new GCE infrastructures without a means to cache build artifacts.

This is going to change.

Not only will open source projects get caching, private repositories running on GCE and OS X will get a caching backend running closer (in networking terms) to their builds, for even faster builds.

What Do You Need to Do?

If your repository is using caching already, there is nothing to do.

However, due to the way caching backends are configured, when your builds switch infrastructures, the first build after the switch creates a new cache, causing a possibly noticeable slowdown.

If your open source project does not have caching enabled and you would like to add caching to it, follow the documentation to set up caching suitable for your repository’s needs.

Here are some examples:

language: ruby
  bundler: true
    - node_modules
language: python
cache: pip
language: node_js
    - node_modules

When will the Change Take Effect?

To tell you the truth, we silently rolled out this new feature late last Wednesday (2016-04-27 19:22 UTC).

Over the following few days, we closely monitored caching backend, and watched out for any potential bug to fix before this blog post.

We are pleased to tell you that there have not been major issues, and, today, we are making this official.

Managing Caches

Caches page (for your OWNER/REPO) shows you all the caches associated with the repository. It allows you to delete caches with a click if you suspect the cache is corrupt.

You can also manage caches with our API.

Questions and Feedback Welcome

We are eager to hear how you find this new exciting feature. If you have questions or feedback, do let us know.

Happy testing!