Skip to content

ci: use gh runners for non docker build jobs #11360

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

Closed
wants to merge 1 commit into from

Conversation

mujahidkay
Copy link
Member

@mujahidkay mujahidkay commented May 8, 2025

Description

We had a significant increase in cost for the month of april for our depot usage which put us way over our plan limit. This PR attempts to fix that by reverting those jobs to GH runners which don't (or won't) necessarily benefit from depot build caching (separate WIP PR).

A detailed analysis is available in the slack thread here.

Security Considerations

None

Scaling Considerations

None

Documentation Considerations

None

Testing Considerations

None. Only reverts the type of runners used.

Upgrade Considerations

None

@mujahidkay mujahidkay requested a review from a team as a code owner May 8, 2025 13:44
@mujahidkay mujahidkay requested a review from AgoricTriage May 8, 2025 13:44
@mujahidkay mujahidkay self-assigned this May 8, 2025
@mujahidkay mujahidkay added the force:integration Force integration tests to run on PR label May 8, 2025
@mhofman
Copy link
Member

mhofman commented May 9, 2025

Let's try to compare the cost per minute against the large GH runners before we switch back.

@mujahidkay
Copy link
Member Author

Closing this as using depot is more cost-effective than GH large runners, as discussed in the slack thread in the description.

@mujahidkay mujahidkay closed this May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
force:integration Force integration tests to run on PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants