Contents

After setting up build automation we also wanted it not to happen only when updating the documentation repository.

Besides hosting documentation, Elegant website also serves as a live demo of the current release. This meant, the website should be regenerated and updated every time when a documented is added or edited, and also when Elegant theme is updated.

Github and Travis doesn’t offer dependent builds out of the box, so the trick goes to ‘signal’ via a github token to trigger a travis-ci build.

As you can see, in line 14, it grabs the github token from environment variable ‘TRATOKEN’ that we’ve defined in travis-ci environment for the build.

This is similar to what we did in the documentation repo to push the built website to another repo.

With this solution in place, when a new commit is merged on ‘master’ branch on the ‘theme’ repo (elegant), travis does get invoked to schedule a build on the documentation repo, thus, rendering the live website with latest templates.