Hey Justin — thanks for the feedback.
[RR] I believe it’s similar. If you are looking for an example, I’d better look to the Polymer Starter Kit. I believe they have more of this stuff out-of-the-box by now.
We changed our build process since then, hence the 404. Sorry, for that. I updated the blog post to point to the original files.
> Making the script executable with git update-index — chmod=+x gpages_build.sh can become tedious for each element. I’ve noticed that in your .travis.yml file, you’ve included a bower install -s …collaborne-build-tools.git along with a after_success: gpages_build.sh. Is this your recommended way of solving the issue or are you doing this for another reason? What’s inside that collaborne-build-tools.git that I should take into consideration? How should I go about it adding this?
[RR] collaborne-build-tools is our internal build tool (open sourcing this is on our TODO list). We basically needed to centralize all the build logic to keep some consistency between all our projects. I updated the links in the blog post to point to the old .travis.yml and gpages_build.sh which work without collaborne-build-tools.
> In Travis CI we need to 2 Environment Variables provided by Github, … GH_REF and GH_TOKEN. Is this something that we have to setup for EVERY repo manually inside Travis CI’s Settings? Or is there a place to set it globally? Looking at your .travis.yml example, I see the env: secure: — Is this where the 2 environment variables are stored and encrypted? If so, how should I go about it?
[RR] Yes, you can set the env: secure instead of configuring them in the UI. Best use the Travis command line tool:
travis encrypt GH_TOKEN=<GH-TOKEN> --add
We normally create a separated GH token per project.
> Upon auto generating the demo & docs to Github Pages, is there a way to automatically update the demo & docs links along w/ the correct badges inside the README.md file? Or does this have to be a manual process? I imagine this can be done via a generator-polymer-init Yeoman template, but if it can be solved w/ .travis.yml or gpages_build.sh script, I think it would be better.
[RR] I’m not sure if I understand the question. We set up the README once, pointing to the demo & docs. The Travis build updates the demo & docs in place, i.e. the URL to the demo & docs doesn’t change.
Hope that helps.