Join GitHub today
Update the travis build to work in stages #948
Improve the CI (test, build, and deploy) process by using build stages rather than a (somewhat hard to understand and arbitrary) build matrix. For now it just improves the readability of the
For clarity, I added two commits showing the build report when something goes wrong. The first is when the website cannot be build, and the second is when there is a linting error. As seen in the images below:
To summarize, Travis will now first lint & build the website (in parallel), and only if both succeed will it try to deploy. That only happens if the commit is on
In the future, with #898 in mind, this would make it easier to build to website in one step, and have it be deployed in another one (if that is even needed
birjolaxew left a comment •
Note that when it comes to building and deploying in two separate stages, storage isn't shared amongst stages - this means that although we can (and should) use a single stage for testing that the build works, we will also have to run the build in the deploy stage.
[Edit] Whoops, didn't submit the inline comment. Guess it'll have to be here instead.