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
Integrate ios_engine debug, profile and release. #39724
Conversation
This provides greater reusability of subbuilds saving an approximate of 6 bots per run.
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.
Total execution time didn't change too much. ~15min
ci/builders/mac_ios_engine.json
Outdated
@@ -89,12 +133,72 @@ | |||
"script": "flutter/sky/tools/create_full_ios_framework.py", | |||
"language": "python3" | |||
}, | |||
{ | |||
"name": "Profile-FlutterMacOS.framework", |
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.
I think I asked this in another PR, but why is building the iOS artifacts called FlutterMacOS.framework
? FlutterMacOS.framework is the macOS embedder artifact...
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.
That was probably an attempt to use a better name than artifacts
, which name should we use here? this is just what is shown in the step name.
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.
Profile-Flutter.xcframework
or Profile-ios-Flutter.xcframework
would be more accurate.
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.
Updated!
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.
This LGTM
@zanderso do you have any objections to combining the runtime modes into one builder?
ci/builders/mac_ios_engine.json
Outdated
@@ -89,12 +133,72 @@ | |||
"script": "flutter/sky/tools/create_full_ios_framework.py", | |||
"language": "python3" | |||
}, | |||
{ | |||
"name": "Profile-FlutterMacOS.framework", |
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.
Profile-Flutter.xcframework
or Profile-ios-Flutter.xcframework
would be more accurate.
My understanding is that the builds for each runtime mode will run in parallel in a separate drone. If that is true, then this lgtm. |
That is correct, everything runs as sub-builds. |
…121020) * 1d7f0c66c Integrate ios_engine debug, profile and release. (flutter/engine#39724) * a37e27b77 [web] Don't include end-of-line characters in line boundary (flutter/engine#39693)
This provides greater reusability of subbuilds saving an approximate of 6 bots per run.
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.