Moving from Travis to GitHub Actions

[ErikSchierboom]

Hello 🙂

Over the last few months we've been transferring all our CI from Travis to GitHub Actions (GHA). We've found that GHA are easier to work with, more reliable, and much much faster.

Based on our success with GHA and increasing intermittent failures on Travis, we have now decided to try and remove Travis from Exercism's org altogether and shift everything to GHA. This issue acts as a call to action if your track is still using Travis.

For most CI checks this should be a transposing from Travis' syntax to GHA syntax, and hopefully quite straightforward (see this PR for an example). However, if you do encounter any issues doing this, please ask on Slack where lots of us now have experience with GHA, or post a comment here and I'll tag relevant people. This would also make a good Hacktoberfest issue for anyone interested in making their first contribution 🙂

If you've already switched this track to GHA, please feel free to close this issue and ignore it.

Thanks!

[wneumann]

Not sure how I missed this issue when it was created, but I'm glad to see this. There's been an issue with the swift track's CircleCI setup for a while that needs fixing, but it wasn't impacting v3 work so I'd been pushing off figuring out how to fix it (I know absolutely nothing about CI setups).

Apparently the current CircleCI setup checks the test-suites against three old (though not as old at the time) versions of Swift, the oldest of which requires the Ruby gem 'Danger' (for some reason) and apparently there's a Ruby version mismatch causing the install of Danger, and thus that check, to fails. Note that Travis is also failing when it tries to fetch configlet.

I'll probably have to pester y'all over in the CI slack channel once I get to working on this.

[cmccandless]

You can also tag @exercism/github-actions for assistance in related PRs.

[iHiD]

Also see https://github.com/exercism/problem-specifications/tree/master/workflows#workflow-templates 🙂

[cmccandless]

Whoever resolves this issue, would you also be willing to look into migrating the Objective C track? The current CI config is a bit messy, but the tooling should be similar to this track.