CI: Use separate job for building Windows deps - #14833
Open
TheLastRar wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of Changes
Splits building dependencies on windows to their own CI job
Rationale behind Changes
The same deps are used across all 6 windows CI builds
This results in us sending 6 concurrent downloads to the same file on every deps update PR, as well as wasting resources building the same thing 6 times.
If one of those runs fails to downloads the deps, we have to wait until the other builds have finished before rerunning.
By using a separate job, we can avoid the above issues.
Suggested Testing Steps
Test CI builds
Also test the cut-release action still works
Did you use AI to help find, test, or implement this issue or feature?
No