chore(ci): add horsepower to build process #6
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
chris13524
reviewed
Sep 3, 2024
jackpooleywc
reviewed
Sep 4, 2024
There was a problem hiding this comment.
I think the limiting factor here is our Swift CI pipeline. The Rust CI pipeline currently takes ~ 5mins, and the Swift CI takes ~ 10mins. They currently run in parallel so we usually wait ~ 10mins for CI to pass. Not sure what the extra cost is here, so I can't weigh in on if this is worth it. My suggestion would be to optimise the Swift pipeline as Rust is currently being built twice, if we can avoid that we might be able to get CI to pass in ~ 5mins or so. I believe the Swift pipeline is also more expensive as it has to run on macOS runners.
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.
No description provided.