Migrate from Travis CI to GitHub Actions for build process
Relequestual opened this issue · 3 comments
Our builds and deploys have stopped working because Travis CI .org is no longer working.
We could migrate to the new .com version, but might as well use GitHub Actions.
This doesn't look too frightening. Here is a relatively simple build/test/deploy workflow for comparison.
EDIT: I'm trialling https://meercode.io as a replacement for the Travis CI dashboard. Tell them I sent you!
Travis CI .com is broken for multiple organisations linked to one GitHub account (for me anyway) so that was a definite non-starter, before you get to the politics/viability of Travis after they fired 50+ developers.
Travis CI .org is no longer working.
oh, damn, had no idea
It's not as trivial as it looks, but I think the biggest hurdle was already cleared when setting up a docker container with all the build dependencies for local development. I think we'll need a custom action, but it looks like it's relatively easy to build an action that just runs the build in a docker container.