...

General requirements

• Team Size:
  • ~1-5 people working on it at the same time.
• Source code hostingNumber of repositories:
  • ~5-20 repositories.
  • Not expected to be checked out many times, mostly for those who actually work on it and by CI server.
• Code review
  • Gerrit (http://gerrithub.io) or Github.
• CI Server
  • Any typical CI server which can connect Gerrit or GitHub, and Binary Storage solutions.
• Build host
  • See https://source.android.com/docs/setup/start/requirements
  • To build AOSP today we need at least 500GB of fast storage and minimum of 64GB RAM.
  • For each additional version or "flavor" of emulator we would need 500GB storage and separate build directory.
  • The server should run latest Ubuntu LTS (also headless).
• Test host (for starters we can run tests directly on build host, but it would be good to split responsibilities).
  • See https://developer.android.com/studio/run/emulator#requirements
  • Needs 16 GB RAM, 64bit OS, 16 GB disk space.
  • A (virtual) display to take screenshots from.
  • If it is a VM, then we need support for nested virtualization. We will be building Goldfish emulator, which is run using QEMU/KVM.
• Binary repository
  • ~100 GB should be good for starters (storing all releases and temporary build artifacts)
  • One emulator archive with Android 14 is ~2 GB, it is only going to grow. Note: in GitHub, each individual file must be smaller than 2 GiB (https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases#storage-and-bandwidth-quotas), which could be easily exceeded with emulator.
  • We would need to store binaries for all releases: at least 3 latest versions (e.g., Android 13, Android 14, Android 15). Maybe also adding flavors to each version in future (with/without additional services).
    
  • Also all artifacts from pending PRs should be stored there

...