-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: use self-hosted runners for CI pipelines #5572
Comments
Hey team! Please add your planning poker estimate with Zenhub @arya2 @dconnolly @gustavovalverde @oxarbitrage @teor2345 |
@gustavovalverde @mpguerra can we be more specific with the scope here? What specific changes are we going to try? It's hard to estimate this ticket without a list of tasks or a list of requirements. |
Larger runners are still limited to 6 hours, but this may bypass ssh issues if done the hard way. https://github.com/actions-runner-controller/actions-runner-controller |
Yeah we might want to scope this first issue as 'try setting up /a/ self-hosted runner for one simple workflow/action' |
I added some steps |
Thanks, that looks good!
I think moving all the sync jobs might be out of scope for an initial ticket. There's no particular urgency, they seem to be working ok. Or did you want this to become a tracking issue? |
I removed that one. |
By the way, if you want a no-maintenance method to achieve that, you can use cirun.io for the same. |
unscheduling for now |
Motivation
Some of our tests, mainly our full sync test, are way above GitHub-hosted runners limits, being the 6 hours timeout the main limitation.
We might want to start testing GitHub self-hosted runners to raise the limits.
Designs
Related Work
Another approach would be using #5551, if we get through their beta waitlist. But this might won't get rid from the 6 hours limit.
The text was updated successfully, but these errors were encountered: