Use larger runners for bottleneck builds of release artifacts #9239
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The Windows jobs still look like a bottleneck, but I'm not sure I want to switch to the extra large runners. |
charliermarsh
approved these changes
Nov 19, 2024
|
Should we use smaller runners for the fast builds or something? Probably a bad idea. |
|
I don't think we can, we're using the GitHub defaults which are small and free. If anything, I'd want to use the fast runners for everything and get the release time down so we don't need to monitor it as long — it's not worth the investment right now though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uses a different runner for builds that take >15m.
Most of the builds finish in ~10 minutes.