-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Travis run environment #34
Comments
seriema
added a commit
that referenced
this issue
Sep 13, 2015
As according to http://docs.travis-ci.com/user/migrating-from-legacy/ Reference #34
seriema
added a commit
that referenced
this issue
Sep 13, 2015
It should speed up the builds a little bit. Hope this doesn’t mess things up sometime in the future when a new version of a package isn’t picked up =P Resources: http://docs.travis-ci.com/user/caching/#Fetching-and-storing-caches http://blog.travis-ci.com/2013-12-05-speed-up-your-builds-cache-your-dep endencies/ Reference #34
seriema
added a commit
that referenced
this issue
Oct 3, 2015
Use new Travis container based infrastructure. As according to http://docs.travis-ci.com/user/migrating-from-legacy/ Cache npm and Bower directories. Hopefully get some build speed improvement, but just good practice otherwise. We should start with npm-shrinkwrap or something to avoid local updates that aren't picked up by Travis because of the caching. Resources: http://docs.travis-ci.com/user/caching/#Fetching-and-storing-caches http://blog.travis-ci.com/2013-12-05-speed-up-your-builds-cache-your-dep endencies/ Closes #34
seriema
added a commit
that referenced
this issue
Oct 3, 2015
Use new Travis container based infrastructure. As according to http://docs.travis-ci.com/user/migrating-from-legacy/ Cache npm and Bower directories. Hopefully get some build speed improvement, but just good practice otherwise. We should start with npm-shrinkwrap or something to avoid local updates that aren't picked up by Travis because of the caching. Resources: http://docs.travis-ci.com/user/caching/#Fetching-and-storing-caches http://blog.travis-ci.com/2013-12-05-speed-up-your-builds-cache-your-dep endencies/ Closes #34
seriema
added a commit
that referenced
this issue
Oct 3, 2015
Use new Travis container based infrastructure. As according to http://docs.travis-ci.com/user/migrating-from-legacy/ Cache npm and Bower directories. Hopefully get some build speed improvement, but just good practice otherwise. We should start with npm-shrinkwrap or something to avoid local updates that aren't picked up by Travis because of the caching. Resources: http://docs.travis-ci.com/user/caching/#Fetching-and-storing-caches http://blog.travis-ci.com/2013-12-05-speed-up-your-builds-cache-your-dep endencies/ Closes #34
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Travis is showing this notice on current builds:
It's simple to upgrade, but I'd also like to investigate the caching possibilities now available for open source projects.
The text was updated successfully, but these errors were encountered: