cimg/android pulls statistics

CircleCI Convenience Images => Android

A Continuous Integration focused Android Docker image built to run on CircleCI

*This image is designed to supercede the legacy CircleCI Android image, circleci/android.*

cimg/android is a Docker image created by CircleCI with continuous integration builds in mind. Each tag contains an Android environment and toolchain. Including several API SDKs, command line tools, build tools, Ant, Gradle, Google Cloud SDK, and more.

Table of Contents

• Getting Started • How This Image Works • Development • Contributing • Additional Resources • License

Getting Started

This image can be used with the CircleCI docker executor. For example:

In the above example, the CircleCI Android Docker image is used for the primary container. More specifically, the tag 2021.08.1 is used meaning the August 2021 snapshot of the image is used. You can now build and test Android projects within the steps for this job.

How This Image Works

This image contains the Android SDK and CLI tools.

Variants

Variant images typically contain the same base software, but with a few additional modifications.

NDK - Native Development Kit

The NDK variant is the same Android image but with the Android NDK installed. Specifically a stable and LTS version. The NDK variant can be used by appending -ndk to the end of an existing cimg/android tag.

Node.js

The Node.js variant is the same Android image but with Node.js also installed. The Node.js variant will be used by appending -node to the end of an existing cimg/android tag.

Browsers

The browsers variant is the same Android image but with Node.js, Java, Selenium, and browser dependencies pre-installed via apt. The browsers variant can be used by appending -browser to the end of an existing cimg/android tag. The browsers variant is designed to work in conjunction with the CircleCI Browser Tools orb. You can use the orb to install a version of Google Chrome and/or Firefox into your build. The image contains all of the supporting tools needed to use both the browser and its driver.

Tagging Scheme

This image has the following tagging scheme:

- The snapshot of the image to use. The available tags and a list of software pre-installed can be found in the Developer Hub.

[-variant] - a variant tag can optionally be added. The available variants can be found above.

Development

Images can be built and run locally with this repository. This has the following requirements:

• local machine of Linux (Ubuntu tested) or macOS • modern version of Bash (v4+) • modern version of Docker Engine (v19.03+)

Cloning For Community Users (no write access to this repository)

Fork this repository on GitHub. When you get your clone URL, you'll want to add --recurse-submodules to the clone command in order to populate the Git submodule contained in this repo. It would look something like this:

If you missed this step and already cloned, you can just run git submodule update --recursive to populate the submodule. Then you can optionally add this repo as an upstream to your own:

Cloning For Maintainers ( you have write access to this repository)

Clone the project with the following command so that you populate the submodule:

Generating Dockerfiles

Dockerfiles can be generated for this image by using the gen-dockerfiles.sh script. For example, you would run the following from the root of the repo:

The generated Dockerfile will be located at ./2021.07/Dockerfile. To build this image locally and try it out, you can run the following:

Building the Dockerfiles

To build the Docker images locally as this repository does, you'll want to run the build-images.sh script:

This would need to be run after generating the Dockerfiles first. When releasing proper images for CircleCI, this script is run from a CircleCI pipeline and not locally.

Publishing Official Images (for Maintainers only)

The individual scripts (above) can be used to create the correct files for an image, and then added to a new git branch, committed, etc. A release script is included to make this process easier. To make a proper release for this image, let's use the fake tag of 2021.07.1, you would run the following from the repo root:

This will automatically create a new Git branch, generate the Dockerfile(s), stage the changes, commit them, and push them to GitHub. The commit message will end with the string [release]. This string is used by CircleCI to know when to push images to Docker Hub. All that would need to be done after that is:

• wait for build to pass on CircleCI • review the PR • merge the PR

The main branch build will then publish a release.

Incorporating Changes

How changes are incorporated into this image depends on where they come from.

build scripts - Changes within the ./shared submodule happen in its own repository. For those changes to affect this image, the submodule needs to be updated. Typically like this:

parent image - By design, when changes happen to a parent image, they don't appear in existing Android images. This is to aid in "determinism" and prevent breaking customer builds. New Android images will automatically pick up the changes.

If you *really* want to publish changes from a parent image into the Android image, you have to build a specific image version as if it was a new image. This will create a new Dockerfile and once published, a new image.

Android specific changes - Editing the Dockerfile.template file in this repo will modify the Android image specifically. Don't forget that to see any of these changes locally, the gen-dockerfiles.sh script will need to be run again (see above).

Contributing

We encourage issues and pull requests against this repository. In order to value your time, here are some things to consider:…

Description from the Docker Hub listing.