tool-test-general.yml had a lot of gnarly, but sharable code. Moving to
a shared, composite workflow.
updates:
- removed the "flutter/" working folder while running; keep the code in
the workspace
- moved android and pub-cache to /opt/
- switched to `flutter pub get` as the last step
- caching still works; but I think we could do better.
Put the Android SDK and pub cache under the workflow's workspace
directory instead of the worker's `$HOME` directory. In order to avoid
the pub cache and Android SDK being nested inside of the Flutter
checkout, this change also moves the Flutter checkout to a subdirectory
of the workspace directory called `flutter`.
---------
Co-authored-by: John "codefu" McDole <codefu@google.com>
- remote repo: set upstream and get tags (flutter tool reqs)
- pull request to flutter: checkout the PR, not the merge commit
- local runs: update utils.dart to safely call terminal width
Now `act -W .github/workflows/tool-test-general.yml` works locally on
the command line.
Future improvements:
- Offer another way to set the "version" rather than tags; this causes a
longer checkout time.
- Multi-proc the tests and use as many cores as possible?
- Solve for packages downloading?
3.5 minutes isn't terrible.
Demonstrates running Linux tool-tests-general running on workflows.
Can be run locally using ACT: `gh act --workflows
".github/workflows/tool-test-general.yml" --secret-file "" --var-file ""
--input-file "" --eventpath ""` - except this works only in VSCode since
tty isn't attached.
