New Circleci Android Docker images - current being deprecated.

Question

New Circleci Android Docker images - current being deprecated.

Closed this issue a year ago · 9 comments

...designed to be faster, more efficient, and most importantly, more reliable. You can learn more about all of the features on our blog post 933. As we begin to deprecate the legacy images, this document provides information on the migration process.

All legacy images have a Docker namespace of circleci, while next-gen images have a Docker namespace of cimg. For example, migrating from the legacy Ruby or Python image to the respective next-gen image can be done as follows:

circleci/ruby:2.3.0 → cimg/ruby:2.3.0
circleci/python:3.8.4 → cimg/python:3.8.4

Images available now

https://circleci.com/developer/images

At the top of the list there is:

cimg/android | An Android Docker image built to run on CircleCI that contains API levels, build & platform tools, and the NDK variant images. | 2023.08

cimg/android

An Android Docker image built to run on CircleCI that contains API levels, build & platform tools, and the NDK variant images.

2023.08

@bdbcat Shouldn't we be using this to build Android now?

We currently are using a docker image

    build-android-arm64:
        docker:
        - image: cimg/android:2021.10.2-ndk
        resource_class: large
        environment:
        - OCPN_TARGET:  android-arm64
        - DEPLOY_USE_ORB: true

and

    build-android-armhf:
        docker:
        - image: cimg/android:2021.10.2-ndk
        resource_class: large
        environment:
        - OCPN_TARGET:  android-armhf

Answer 1 · 2023-08-08T19:18:50.000Z

Whoops I just saw this page for more details
https://circleci.com/developer/images/image/cimg/android

jobs:
  build:
    docker:
      - image: cimg/android:2023.08
    steps:
      - checkout
      - run: ./gradlew androidDependencies
      - run: ./gradlew lint test

In the above example, the CircleCI Android Docker image is used for the primary container. More specifically, the tag 2023.08 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.

Additionally, you can use the Android Orb to access the Docker executor and configure your image in a standardized way.

While it is possible to use this image for emulation, it's highly recommended to use the machine image instead.

Answer 2 · 2023-08-08T19:22:06.000Z

Here is the page for using the machine image, which I they recommend.

https://circleci.com/developer/machine/image/android

Answer 3 · 2023-08-08T19:22:43.000Z

Do you want me to just start using testplugin FE2 now, or wait?

Answer 4 · 2023-08-08T19:24:06.000Z

I think the android config.yml complies with the modern requirements, so I am just going to start using TP

Answer 5 · 2023-08-16T09:56:46.000Z

This should actually have been filed against both the TP and shipdriver templates. Shipdriver issue here

Answer 6 · 2023-10-26T13:15:00.000Z

@bdbcat @leamas Should this be closed now?

Answer 7 · 2023-10-26T13:20:27.000Z

The shipdriver issue is closed. No idea about TP.

Answer 8 · 2023-10-26T13:22:37.000Z

There is an issue in TP Testplugin not done yet. Closing.

Answer 9 · 2023-10-26T13:31:28.000Z

You see how these things ends up. Issues which requires changes in the actual plugin code needs to be filed against TP and/or shipdriver, usually both.

The rule of thumb when determining where to file an a issue is "what does need to be modified". If there is a need to modify something in opencpn/plugins, this is the place to file it.

OTOH, if there is a need to modify the templates, the templates are the place to file bugs.