Google employee? See go/chrome-gms for more info.
The standard way of adding the Google Play services as a dependency to a project is to import it through the Android SDK manager as a Maven repository. That repository contains multiple versions of the library split into separate APIs (for example Cast, GCM, Android Pay, etc). To avoid downloading a lot of data we don't need to build Chrome, android checkouts of Chromium download an archive containing only the APIs we currently need in Chrome, and in a single version.
The up to date list of clients and version used can be seen in //build/android/play_services/config.json.
Note: If you are working on a feature that requires different or more recent APIs, you will need to locally download the Google Play services SDK repository.
The simplest way to download the latest SDK is to run:
Check out the help of that script for more info.
As explained above, the default checkout has access to only a specific set of APIs during builds. If your CL depends on some APIs that are not included in the build, you will need file an issue to request an update of our dependencies.
Not doing so could make the CL fail on the trybots and commit queue. Even if it passes, it might fail on the internal bots and result in the CL getting reverted, so please make sure the APIs are available to the bots before submitting.