Skip to content

dt: allow DEVTOOLS_TOOL_FLUTTER_FROM_PATH to be used in CI scripts - #9999

Merged
srawlins merged 1 commit into
flutter:masterfrom
srawlins:setup-dir
Sep 3, 2026
Merged

dt: allow DEVTOOLS_TOOL_FLUTTER_FROM_PATH to be used in CI scripts#9999
srawlins merged 1 commit into
flutter:masterfrom
srawlins:setup-dir

Conversation

@srawlins

@srawlins srawlins commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This is for the process of moving devtools to the Dart SDK repo. This avoids the need to create symlinks over in that workflow. We can just use DEVTOOLS_TOOL_FLUTTER_FROM_PATH.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@override
Future<void> runCommand(ArgResults topLevelResults) {
final flutterFromPathEnv =
Platform.environment[_flutterFromPathEnvVar]?.isNotEmpty == true;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we check that this flag == true? or is checking its presence sufficient? What if someone sets it to false thinking that will disable this behavior?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could, I agree it would be surprising if someone set it to false, and we acted like it was true. But this is the existing behavior in dt:

if [ ! -z "$DEVTOOLS_TOOL_FLUTTER_FROM_PATH" ]; then

I'll send a follow-up, fixing this in all places.

@kenzieschmoll kenzieschmoll left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one comment but lgtm

@srawlins
srawlins merged commit 8bcd111 into flutter:master Sep 3, 2026
50 of 52 checks passed
@srawlins
srawlins deleted the setup-dir branch September 3, 2026 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants