Google Play
-
Introduced in GitLab 15.10 with a flag named
google_play_integration
. Disabled by default. -
Generally available in GitLab 15.11. Feature flag
google_play_integration
removed.
This feature is part of Mobile DevOps developed by GitLab Incubation Engineering. The feature is still in development, but you can:
With the Google Play integration, you can configure your CI/CD pipelines to connect to the Google Play Console to build and release apps for Android devices.
The Google Play integration works out of the box with fastlane. You can also use this integration with other build tools.
Enable the integration in GitLab
Prerequisites:
- You must have a Google Play Console developer account.
- You must generate a new service account key for your project from the Google Cloud console.
To enable the Google Play integration in GitLab:
- On the left sidebar, select Search or go to and find your project.
- Select Settings > Integrations.
- Select Google Play.
- In Enable integration, select the Active checkbox.
- In Package name, enter the package name of the app (for example,
com.gitlab.app_name
). - Optional. Under Protected branches and tags only, select the Only set variables on protected branches and tags checkbox.
- In Service account key (.JSON), drag or upload your key file.
- Optional. Select Test settings.
- Select Save changes.
After you enable the integration, the global variables $SUPPLY_PACKAGE_NAME
and $SUPPLY_JSON_KEY_DATA
are created for CI/CD use.
CI/CD variable security
Malicious code pushed to your .gitlab-ci.yml
file could compromise your variables, including $SUPPLY_JSON_KEY_DATA
, and send them to a third-party server. For more information, see CI/CD variable security.
Enable the integration in fastlane
To enable the integration in fastlane and upload the build to the given track in Google Play, you can add the following code to your app’s fastlane/Fastfile
:
upload_to_play_store(
track: 'internal',
aab: '../build/app/outputs/bundle/release/app-release.aab'
)