Files
flutter/bin/internal
engine-flutter-autoroll 90819b75bb Roll engine 0e0e0a98f511..015c0246aebc (3 commits) (#29464)
0e0e0a98f5...015c0246ae

git log 0e0e0a98f5111ebf4032ef25eaf568f19867ecf1..015c0246aebc6fc23f30004e3319b6d1e85a885a --no-merges --oneline
015c0246a Fix log level typo from ERROR to INFO (flutter/engine#8180)
c033aa469 Fix include of libzx. (flutter/engine#8181)
d92f93730 Add flag to allow only building full sdk on release to speed up bots (flutter/engine#8080)

The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff (jsimmons@google.com), and stop
the roller if necessary.
2019-03-15 22:45:36 -04: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.