{"push_id":682848509,"size":1,"distinct_size":1,"ref":"refs/heads/travis-containers","head":"04cb565f0d0947b8a9ff3db4ea09d9526aa9f646","before":"4c2502f025079a72a468008520b3ca41408354dc","commits":[{"sha":"04cb565f0d0947b8a9ff3db4ea09d9526aa9f646","author":{"email":"78b6854e22ab09d4ae3dac29b92052963103b33e@kalnitsky.org","name":"Igor Kalnitsky"},"message":"Improve Travis CI configuration\n\n1. Use container-based infra on Travis CI\n\n   Since we run only unit tests in Holocron, it's better to use\n   container-based infrastructure on Travis CI. Why? Because it\n   provides:\n\n   * fast start up (no need to wait for free vm)\n   * ability the use caches\n\n   http://docs.travis-ci.com/user/workers/container-based-infrastructure/\n\n2. Use pip caching on Travis CI\n\n   It makes sense to use pip caching on Travis CI because we have\n   different tox envs with almost the same dependencies. With pip\n   caching we won't download deps again for another tox env and that\n   should boost up tests execution time.\n\n   http://docs.travis-ci.com/user/caching/\n\n3. Run builds not only for master branch\n\n   Honestly, I don't know why it was so, but there are no reasons why\n   we shouldn't run CI for other branches.\n\n4. Remove OS X builds\n\n   Currently there's no python setup for OS X. Moreover, the feature\n   is completely experimental and turned off by default. If it doesn't\n   work now, so why do we have it config? :)","distinct":true,"url":"https://api.github.com/repos/ikalnitsky/holocron/commits/04cb565f0d0947b8a9ff3db4ea09d9526aa9f646"}]}