Skip to content
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

Migrate runners #89

Merged
merged 5 commits into from
Jan 10, 2024
Merged

Migrate runners #89

merged 5 commits into from
Jan 10, 2024

Conversation

njooma
Copy link
Member

@njooma njooma commented Jan 10, 2024

From Slack, we should move our workflows away from self-hosted runners to either github or buildjet hosted:

github runners start up faster (we host the rdk-devenv image on github, so it's faster for it to pull the image) so are best for small jobs, and better than doing a 2-core runner on buildjet. Anything that really needs 4 cores or more than 4GB of ram should use buildjet probably, and scale appropriately. Typically 4 or 8 core is the right answer. I've not seen a job that can really make full use of 16 cores for a full run (though if you've got one, then it's worth considering.)

@njooma njooma requested a review from a team as a code owner January 10, 2024 20:42
@njooma njooma requested review from stuqdog and purplenicole730 and removed request for a team January 10, 2024 20:42
@njooma njooma merged commit a7b589f into viamrobotics:main Jan 10, 2024
4 checks passed
@njooma njooma deleted the migrate-runners branch January 10, 2024 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants