@@ -34,7 +34,7 @@ Software not on the above lists may be available, but cannot be relied upon if U
You need to tag the builds that need the Android tooling in your `.gitlab-ci.yml` file with the `android` tag. (If you're unfamiliar with what a `.gitlab-ci.yml` file is, [GitLab describes it here.](https://docs.gitlab.com/ee/ci/yaml/gitlab_ci_yaml.html)) An example is below. This should only be done for jobs where the Android SDK tools are directly required, as job capacity is very limited.
When using the `android` tag, need to ensure that `/android-sdk/platform-tools/` is in your `$PATH` environment variable, as well as setting the `$ANDROID_HOME` environment variable to `/android-sdk`. Both of these can be done in a `before_script` if you have multiple jobs that use the `android` tag, or done in the `script` part of your job for just one.
When using the `android` tag, you need to ensure that `/android-sdk/platform-tools/` is in your `$PATH` environment variable, as well as setting the `$ANDROID_HOME` environment variable to `/android-sdk`. Both of these can be done in a `before_script` if you have multiple jobs that use the `android` tag, or done in the `script` part of your job for just one.
You may optionally want to add `/usr/local/go/bin` to your `$PATH` if you plan to build Go programs for Android in your job, such as building client bindings.
