flutter/bin/internal
engine-flutter-autoroll 1c0385be7c
9e8f8d088 Drop android_sdk_downloader in favor of cipd (flutter/engine#8087) (#29115)
21342863aa...9e8f8d0889

git log 21342863aa6018af53c09af2a3e7aa432a6cc844..9e8f8d0889ec04b54def0bf917321a27006623b0 --no-merges --oneline
9e8f8d088 Drop android_sdk_downloader in favor of cipd (flutter/engine#8087)

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 (mklim@google.com), and stop
the roller if necessary.
2019-03-09 19:16:28 -05:00
..
engine.merge_method Switch engine.merge_method back to squash (#24319) 2018-11-13 17:12:36 -08:00
engine.version 9e8f8d088 Drop android_sdk_downloader in favor of cipd (flutter/engine#8087) (#29115) 2019-03-09 19:16:28 -05:00
goldens.version Roll engine 4f54a1d...2e97618 (#28899) 2019-03-05 18:18:44 -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 Check powershell version. (#27596) 2019-02-06 14:37:47 -08:00
update_dart_sdk.sh Ensure that Dart SDK dirs have appropriate permissions (#26315) 2019-02-15 11:03:57 -05: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.