• Greg Spencer's avatar
    Be more strict about finding version number attached to a revision. (#28527) · 7ab3bc71
    Greg Spencer authored
    When we package Flutter, we used to find the "current" tag (which is the version number) by starting at the revision we are building on and looking backwards in time to find the most recent tag. This causes problems on release builds when we failed to tag properly.
    
    This PR makes the packaging script be more strict by requiring the given revision to itself have a tag, but only when we're publishing the result. When we're not publishing the result, it's more lenient, since otherwise we couldn't test packaging on non-release commits.
    
    I also renamed ProcessRunnerException to PreparePackageException, since we were using that exception more generally than just for processes.
    7ab3bc71
Name
Last commit
Last update
..
test Loading commit data...
README.md Loading commit data...
VERSION_LINUX_NDK Loading commit data...
VERSION_LINUX_SDK Loading commit data...
VERSION_MACOSX_NDK Loading commit data...
VERSION_MACOSX_SDK Loading commit data...
VERSION_WIN_SDK Loading commit data...
analyze-sample-code.dart Loading commit data...
analyze.dart Loading commit data...
cirrus_setup.sh Loading commit data...
codelabs_build_test.sh Loading commit data...
deploy_gallery.sh Loading commit data...
docs.sh Loading commit data...
download_android_tools.py Loading commit data...
find_depot_tools.py Loading commit data...
prepare_package.dart Loading commit data...
pubspec.yaml Loading commit data...
run_command.dart Loading commit data...
test.dart Loading commit data...
upload_android_tools.py Loading commit data...