[!] NOTE: Travis-CI has launched Bundler caching: http://about.travis-ci.org/docs/user/caching/
WAD is a little script that replaces the usual
bundle install on Travis-CI. It installs the bundle and uploads it to Amazon S3 to speed up consecutive runs.
Download the script and put it in your project. It doesn't really matter where you store it. We assume you're using
bin/ in the following examples.
$ curl -o bin/wad https://raw.github.com/Fingertips/WAD/master/bin/wad
Now make the script executable.
$ chmod +x bin/wad
Add and commit it to your source repository.
Travis-CI offers a number of configuration options for stuff that can ran around the build. The actual building should happen with the
script: bundle exec rake test:all
Before this happens we need to keep Travis-CI from installing the bundle and do it ourselves.
install: "bin/wad" script: "bundle exec rake test:all"
Please refer to the Travis documentation if you need to do something more elaborate.
If you always want to run the latest version of WAD, you can set it up like this:
install: "curl https://raw.github.com/Fingertips/WAD/master/bin/wad | ruby" script: "bundle exec rake test:all"
Note that this opens up an attack vector! For example, if someone manages to poision the DNS server used by Travis they can run arbitrary code.
The WAD script needs to know where and how to access S3. You can do this with three environment variables. The S3 region, the bucket name and the S3 credentials.
The region and bucket name are relatively easy:
env: global: - S3_REGION=eu-west-1 - S3_BUCKET_NAME=unique-wad-bucket-name
You don't have to configure the region if you're using
eu-west-1, the default.
The hard part is configuring the credentials, because they need to be signed. First concatenate your key and secret separated by a semicolon, like so:
Then you use the Travis-CI command line utility to sign it. Replace
account/reponame with the same GitHub account and repository name you've configured on Travis-CI.
$ travis encrypt S3_CREDENTIALS="XXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" --repo account/reponame
When all of that is done, you should end up with something like this:
install: "bin/wad" script: "bundle exec rake test:all" env: global: - S3_BUCKET_NAME=unique-wad-bucket-name - S3_REGION=eu-west-1 - secure: "OTpNPEmXlMm70P4y6sE419Rr…"
If you're already using other encrypted variables you can add another
secure key to the configuration or re-encrypt all of the settings. Please read Travis-CI documentation to figure out how that works. Good luck!
WAD doesn't automatically create a bucket for you. Please create one with the AWS console or the S3 tool of your choice.
In some cases you can get network errors on Travis. Currently WAD does not retry bundle uploads or downloads. You can use the
travis_retry tool if you run into this often:
install: travis_retry bin/wad
Note that WAD doesn't clean up old bundles for you. If you change Gemfile.lock a lot and the bucket becomes very large, you probably want to clean out old bundles once in a while.
There are two reasons:
- Installing gems is relatively slow and would unnecessarily slow down the build.
- We wanted WAD to be completely standalone and only require the Ruby stdlib.
WAD is freely distributable under the terms of an MIT-style license. See COPYING or http://www.opensource.org/licenses/mit-license.php.