flutter/bin/internal
liyuqian 57c2fac14a
Add engine merge method configuration (#23953)
In order for this to take effect, https://skia-review.googlesource.com/c/buildbot/+/167200
needs to be landed and deployed.

The /bin/internal/engine.merge_method file controls how we merge a pull
request created by the engine auto-roller. If it's squash, there's only one
commit for a pull request no matter how many engine commits there are inside
that pull request. If it's rebase, the number of commits in the framework is
equal to the number of engine commits in the pull request. The latter method is
easier to detect regressions but cost more test resources.
2018-11-07 13:06:38 -08:00
..
engine.merge_method Add engine merge method configuration (#23953) 2018-11-07 13:06:38 -08:00
engine.version Roll engine e64af7510e89..2494abdda728 (2 commits) (#24065) 2018-11-07 15:03:19 -05:00
goldens.version BottomNavigationBar: bug fix for dealing with animations with shifting tabs (#22264) 2018-11-07 09:20:27 -08:00
gradle_wrapper.version Make artifacts URLs configurable. (#13380) 2017-12-07 16:30:23 +01:00
material_fonts.version Make artifacts URLs configurable. (#13380) 2017-12-07 16:30:23 +01:00
README.md Add engine merge method configuration (#23953) 2018-11-07 13:06:38 -08:00
update_dart_sdk.ps1 update_dart_sdk.ps1: Fall back to Invoke-WebRequest if BITS fails (#19873) 2018-07-27 14:29:20 -07:00
update_dart_sdk.sh Prompt a solution message when flutter tools network fail in China (#16244) 2018-04-06 18:44:05 -07:00

Dart SDK dependency

The bin/internal/engine.version file controls which version of the Flutter engine to use. The file contains the commit hash of a commit in the https://github.com/flutter/engine repository. That hash must have successfully been compiled on https://build.chromium.org/p/client.flutter/ and had its artifacts (the binaries that run on Android and iOS, the compiler, etc) successfully uploaded to Google Cloud Storage.

The /bin/internal/engine.merge_method file controls how we merge a pull request created by the engine auto-roller. If it's squash, there's only one commit for a pull request no matter how many engine commits there are inside that pull request. If it's rebase, the number of commits in the framework is equal to the number of engine commits in the pull request. The latter method makes it easier to detect regressions but costs more test resources.