Set up automatic builds with Travis CI
colinbrislawn opened this issue · comments
Part of a larger goal to make the site easier to edit.
https://travis-ci.org/getting_started
http://blog.mathieu-leplatre.info/publish-your-pelican-blog-on-github-pages-via-travis-ci.html
http://www.andrewaitken.com/tag/travis-ci/
Integration with Travis-CI fully functional! Stop manually pushing to gh-pages and let Travis do it.
Those two tutorials assume significant experience with both Travis and Git. This was a learning experience to say the least.
More than half the build time seems to be installing Pelican. Let's get set up catching properly to maintain blindingly fast builds.
https://blog.travis-ci.com/2013-12-05-speed-up-your-builds-cache-your-dependencies/
https://docs.travis-ci.com/user/caching/#pip-cache
https://github.com/iKevinY/iKevinY.github.io/blob/src/.travis.yml
http://www.vaibhavsagar.com/blog/2015/02/01/blog-setup/
Caching with pip takes about as long as installing directly. I'll look into installing and / or caching with conda.
Nope. Caching works best for long builds that produce small files. Pelican is a short build. I'll retire this for the time being.
Maybe we can cache both the software environment and also the pelican website.
Also, I'm not sure I've turned on cashing as shown here!
AFAIK a 60 second build is pretty good. Just using a git pull depth of 1 and the light pelican build makes this very fast. Cashing takes as much time as the pip install.
Fruitless? 🚫 🍏 🍌 🍓 🤷♂️