797b39e9b2
Creates a new (hidden) flutter command 'ide-config' that will create and/or update
existing .iml files and some files under the .idea directory, as well as
removing existing *.iml files and the .idea directory.
It also:
* Adds *.iml to the .gitignore
* Removes existing .iml files from the repo, and moves them to the
packages/flutter_tools/ide_templates/intellij directory.
* Adds a flag to ide-config ('--update-templates') that will take any new .iml
files in the flutter tree and add them to the existing templates.
- If --overwrite is also specified, then all existing templates will also
be overwritten with the contents from the flutter tree, and any that have
been deleted from the flutter tree will also be removed from the
templates.
* Added new run configurations for all existing app targets that will now also
be automatically added to IntelliJ.
* Setting up the environment also includes setting the coding style guidelines
and the git VCS.
* Note that after this PR lands, Flutter developers will need to run it once to
re-create the .iml files and configuration files that have been removed.
After this PR lands, .iml files will no longer appear in the untracked files
section for git.
|
||
|---|---|---|
| .. | ||
| .gitignore | ||
| analyze-sample-code.dart | ||
| docs.sh | ||
| download_android_tools.py | ||
| find_depot_tools.py | ||
| pubspec.yaml | ||
| README.md | ||
| test.dart | ||
| travis_install.sh | ||
| travis_setup.sh | ||
| travis_upload.sh | ||
| upload_android_tools.py | ||
| VERSION_LINUX_NDK | ||
| VERSION_LINUX_SDK | ||
| VERSION_MACOSX_NDK | ||
| VERSION_MACOSX_SDK | ||
| VERSION_WIN_SDK | ||
Flutter's Build Infrastructure
This directory exists to support building Flutter on our build infrastructure.
The results of such builds are viewable at:
- https://build.chromium.org/p/client.flutter/waterfall
- https://travis-ci.org/flutter/flutter/builds (limited checking used just for PRs on github)
The external master pages for the chromium infra bots do not allow forcing new builds. Contact @eseidelGoogle or another member of Google's Flutter team if you need to do that.
The Travis-based bots are trivial, and just run a couple of shell scripts. The rest of this document discusses only the chromium infra bots.
This infrastructure is broken into two parts. A buildbot master specified by our builders.pyl file, and a set of recipes which we run on that master. Both of these technologies are highly specific to Google's Chromium project. We're just borrowing some of their infrastructure.
Prerequisites
- install depot_tools
- Python package installer:
sudo apt-get install python-pip - Python coverage package (only needed for
training_simulation):sudo pip install coverage
Getting the code
The following will get way more than just recipe code, but it will get the recipe code:
mkdir chrome_infra
cd chrome_infra
fetch infra
More detailed instructions can be found here.
Most of the functionality for recipes comes from recipe_modules, which are
unfortunately spread to many separate repositories. After checking out the code
search for files named api.py or example.py under infra/build.
Editing a recipe
Flutter has one recipe per repository. Currently flutter/flutter and flutter/engine:
- build/scripts/slave/recipes/flutter/flutter.py
- build/scripts/slave/recipes/flutter/engine.py
Recipes are just Python. They are documented by the luci/recipes-py github project.
The typical cycle for editing a recipe is:
- Make your edits (probably to files in
//chrome_infra/build/scripts/slave/recipes/flutter). - Run
build/scripts/slave/recipes.py --use-bootstrap test trainto update expected files - Run
build/scripts/tools/run_recipe.py flutter/<repo> slavename=<slavename> mastername=client.flutter buildername=<buildername>where<repo>is one offlutterorengine, andslavenameandbuildernamecan be looked up from the Build Properties section of a recent build. - Upload the patch (
git commit,git cl upload) and send it to someone in therecipes/flutter/OWNERSfile for review.
Editing the client.flutter buildbot master
Flutter uses Chromium's fancy builders.pyl master generation system. Chromium hosts 100s (if not 1000s) of buildbot masters and thus has lots of infrastructure for turning them up and down. Eventually all of buildbot is planned to be replaced by other infrastructure, but for now flutter has its own client.flutter master.
You would need to edit client.flutter's master in order to add slaves (talk to @eseidelGoogle), add builder groups, or to change the html layout of https://build.chromium.org/p/client.flutter. Carefully follow the builders.pyl docs to do so.
Future Directions
We would like to host our own recipes instead of storing them in build. Support for cross-repository recipes is in-progress. If you view the git log of this directory, you'll see we initially tried, but it's not quite ready.
Android Tools
Instructions to update the Android Tools version that the bots download by executing download_android_tools.py.
How to update Android SDK on Google Cloud Storage
-
Run Android SDK Manager and update packages
$ dev/bots/android_tools/sdk/tools/android update sdkUseandroid.baton Windows. -
Choose/Update packages The following packages are currently installed:
- Android SDK Tools
- Android SDK platform-tools
- Android SDK Build-tools 24.0.3
- Android 6.0 (API 23)
- SDK Platform 23
- Extras
- Android Support Repository
- Google Play services
-
Run upload_android_tools.py -t sdk
$ dev/bots/upload_android_tools.py -t sdk
How to update Android NDK on Google Cloud Storage
-
Download a new NDK binary (e.g. android-ndk-r10e-linux-x86_64.bin)
-
cd dev/bots/android_tools
$ cd dev/bots/android_tools -
Remove the old ndk directory
$ rm -rf ndk -
Run the new NDK binary file
$ ./android-ndk-r10e-linux-x86_64.bin -
Rename the extracted directory to ndk
$ mv android-ndk-r10e ndk -
Run upload_android_tools.py -t ndk
$ cd ../..$ dev/bots/upload_android_tools.py -t ndk