I just flicked the switch that continuously deploys meta every time we have a successful build (which triggers a merge of tests-passed branch)
There are quite a few reasons for this.
Our default docker templates now target the “tests-passed” branch, I want meta to be a place where people can go to always confidently see what it looks like.
This keeps us honest as developers, in the past I blogged about the importance of smoke tests, if for any reason we break master we now have a very clear public warning sign. We will stop everything and fix master and ensure an automated test will stop incidents like this in future.
I really want meta to go through every release of Discourse, that ensures we don’t have boobytrap migrations and other weird upgrade conditions that are untested.
I really like doing this and think it will lead to a more stable master branch in the long term.
This new system is in effect now