Move from circleci to github actions

[lahabana]

What happened?

github actions is free for OSS so we'd save some money.

In the past there were blockers to do this. The ones I remember of were: parallel runs and arm worker.
We should first check if we have everything to move to github actions and then maybe do it.

Apparently parallel runs is possible with: https://rubyyagi.com/how-to-run-tests-in-parallel-in-github-actions/

[slonka]

I found GH actions limits:

we use 400 minutes per one run (including parallel runs) so that would only last for 5 runes. If the table above is right we might want to just close this or consider self-hosted runners.

[michaelbeaumont]

We need to compare the price of credits/minutes and check the number of free minutes for CircleCI

[slonka]

It's up to* 6000 build minutes / month

* - using small docker resource class which we're probably not using

[aktech]

Hey @slonka Sorry for jumping on this. "self-hosted" got my attention.

If the table above is right we might want to just close this or consider self-hosted runners.

You can achieve this with https://cirun.io It creates on demand runners for GitHub Actions on your cloud and manages the complete lifecycle. You simply connect your cloud provider and define what runners you need in a simple yaml file and that's it.

See https://docs.cirun.io/reference/examples.html#aws for example. Let me know if you have any questions. I am the creator of Cirun.

[slonka]

Hi @aktech - if you can show that it is significantly more cost efficient then we will consider it.

[aktech]

Hey @slonka sure I'll share some numbers/demo for the same, also just to clarify Cirun.io is free for Open Source, you only pay to your cloud provider for the VM usage.

[lahabana]

Free for org is different from OSS free. AFAIU github actions is 100% free for OSS projects.

[aktech]

Free for org is different from OSS free. AFAIU github actions is 100% free for OSS projects.

That's absolutely true, my suggestion was for ARM runners, which are only available via self-hosted.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[lahabana]

One thing we've discussed with @slonka to enable a progressive move is to have a workflow that waits for circleci checks to be green.
This way downstream automation can rely on this and we can progressively move things from circleCI to GH actions by extending this workflow.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[michaelbeaumont]

I guess @jijiechen you're working on this? Duplicate issue or still useful? @lahabana

[jijiechen]

Closing this as we've done this by a few PRs.