This directory exists to support building Flutter on our build infrastructure.
The results of such builds are viewable at:
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.
sudo apt-get install python-piptraining_simulation): sudo pip install coverageThe 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.
Flutter has one recipe per repository. Currently flutter/flutter and flutter/engine:
Recipes are just Python. They are documented by the luci/recipes-py github project.
The typical cycle for editing a recipe is:
//chrome_infra/build/scripts/slave/recipes/flutter).build/scripts/slave/recipes.py --use-bootstrap test train to update expected filesbuild/scripts/tools/run_recipe.py flutter/<repo> slavename=<slavename> mastername=client.flutter buildername=<buildername> where <repo> is one of flutter or engine, and slavename and buildername can be looked up from the Build Properties section of a recent build.git commit, git cl upload) and send it to someone in the recipes/flutter/OWNERS file for review.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.
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.
Instructions to update the Android Tools version that the bots download by executing download_android_tools.py.
Run Android SDK Manager and update packages $ dev/bots/android_tools/sdk/tools/android update sdk Use android.bat on Windows.
Choose/Update packages The following packages are currently installed:
Run upload_android_tools.py -t sdk $ dev/bots/upload_android_tools.py -t sdk
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