-
Notifications
You must be signed in to change notification settings - Fork 3
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
[plz rebase merge] Cache Sentry Builds to S3 #3392
Conversation
ebd2236
to
edf4375
Compare
edf4375
to
ce1e32b
Compare
✔️ Deploy Preview for fractal-dev canceled. 🔨 Explore the source changes: af11cb3 🔍 Inspect the deploy log: https://app.netlify.com/sites/fractal-dev/deploys/6104296adf1f50000759fdd9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks I've been meaning to get around to this for a long time
8369e5a
8369e5a
to
af11cb3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI part looks good to me
Description
This PR should greatly reduce protocol build time by building Sentry ahead of time! Note that this PR should go after #3388.
Implementation
I first wrote a workflow job to build Sentry/Crashpad on Windows/Linux/macOS. Then, I added Sentry to our protocol
cmake
while removing the old Sentry pipeline.Importantly, we have to make sure not to build Sentry tests on Windows, since there's an outstanding issue solved by getsentry/sentry-native#583. Once that fix is in, we can bump our Sentry version to make our CI a little more robust, though I don't think we want to build tests in any case.
Note that Sentry by default builds with
-O3
, as I manually confirmed in itscmake
configuration. I only chose build typeRelease
to get rid of debug symbols.