Exclude flutter doctor IDE validators in CI environments#13816
Exclude flutter doctor IDE validators in CI environments#13816Hixie merged 1 commit intoflutter:masterfrom
Conversation
bdd416f to
70c3f23
Compare
|
cc @tvolkert |
|
I'm curious what your use case is that causes you to run |
Not necessarily. For example, in the above mentioned Dockerfile one can forget to install one of: via the Even though the Running |
|
Thanks for the contribution @alibitek! |
|
I need to revert this because it broke one of our tests (probably a test running on a bot that's verifying the IDE stuff). I'll post the logs momentarily. |
|
The tests that failed were: The logs were respectively: |
|
Yeah, both of these tests are looking for "Android Studio at" in the output. @alibitek Would you mind making the appropriate changes to those tests and resubmitting the PR? |
|
@Hixie I will make the appropriate changes to those tests and resubmit the PR. |
…flutter#14196) * Revert "Bump async, http, and vm_service_client packages (flutter#14136)" This reverts commit 7ffcce8. * Revert "Exclude flutter doctor IDE validators in CI environments (flutter#13816)" This reverts commit 3258c54.
flutter doctorexits with a non-zero status code when one of the defined IDE validators returnsValidationType.missing:Due to this, one cannot use the exit status of
flutter doctorcommand in a CI environment to determine whether flutter system requirements are met.For example, in GitLab CI, the GitLab Runner stops executing when it encounters a command within a job that exits with a non zero code.
I had to use
RUN flutter doctor || exit 0instead ofRUN flutter doctorto prevent the build job from failing after runningflutter doctorin a Docker container image based on Debian Stretch where no IDE is installed.