Repository navigation
Generic way to support ENV variables from ci.yaml #140457
Description
Activity
- added a commit that references this issue
on Dec 21, 2023 https://flutter-review.googlesource.com/c/recipes/+/53301 to fix the issue.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Jan 22, 2024
Different repositories and different targets may depend on certain env. variables to run test in different ways. Instead of specific logics for each env. variable, we should have a generic support for different env. variables.
Ideal case, people just define these values in .ci.yaml targets, and these values will be auto populated to ENV when running tests.
Example env. variable support: