Buildkite CI service transition
We have been looking CI solutions due to some changes in the service we’ve been provided by shippable.
One of the options we’ve been testing is Buildkite. As such you’ve probably seen a GitHub status for buildkite.
We have setup things such that Shippable status is still considered required and the buildkite status is optional at this stage.
One thing is that any PR that was submitted before the buildkite infrastructure was committed into the master needs to be rebased on master to get the buildkite files. You can tell if <ZEPHYROOT>/.buildkite/pipeline.yml exists for you.
If you have any questions you can find me either via email or on slack on the #infrastructure channel.