chore: strip Linux backend debug info and upload to Sentry #3188
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.
Summary
It turns out that even though we include the debug info in the Linux backend bindings that we ship with Firefly, Sentry does not symbolicate errors from them (in the
firefly-desktop
package) without receiving the debug info through a CLI upload. Therefore, we can upload the debug info to Sentry during the CI build and then strip it from the bindings that will be included in a build in Firefly. This reduces the size of the bindings from approximately 701 MB to approximately 37 MB.Changelog
Relevant Issues
Fixes #2568
Type of Change
Testing
Platforms
Please select any platforms where your changes have been tested.
Instructions
Triggered crashes to check if Sentry recognized the corresponding debug file. Also tested upload with GHA
Checklist