perf(ci): Use Debug configuration for CI screenshots#111
Merged
Conversation
Switch from Release to Debug build configuration for the generate_screenshots_ci lane. Release builds include Whole Module Optimization and aggressive compiler passes that significantly increase build time (~9 min vs ~3-4 min). For CI visual regression testing with Sentry, Debug builds are acceptable since UI layout is identical between configurations. The full generate_screenshots lane remains Release for App Store submissions. Expected savings: ~5-6 minutes per CI run.
Simplify the job and step names for cleaner CI output.
Remove invalid github.job.name from concurrency group - this context variable is not available at workflow level and was causing the cancel-in-progress to not work correctly.
Sentry Build Distribution
|
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
1 participant
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.
Switch from Release to Debug build configuration for the
generate_screenshots_cifastlane lane.Fastlane's
capture_screenshotsdefaults to Release builds, which include Whole Module Optimization and aggressive compiler passes. Analysis of recent CI runs showed:The build phase alone accounts for ~9 minutes in Release vs ~3-4 minutes in Debug.
For CI visual regression testing with Sentry, Debug builds are acceptable since the UI layout is identical between configurations. The full
generate_screenshotslane (used for App Store submissions) remains unchanged and will continue to use Release configuration.Expected savings: ~5-6 minutes per PR workflow run.