Android Image Deprecations and EOL for 2024

Announcements Notices
,
7

OK, this is where we go down a rabbit hole.

I guess you are working from examples found on the ORB page here

Now what the docs on this page do not make clear at all is that “android/android-machine” is just a placeholder. The image name loaded is

image: android:<< parameters.tag >>

Where tag is a valid value from the list on the page I linked to. So “android/android-machine” which is just “android” shares the same tag list as “cimg/android” images.

I can run the following workflow without errors, I had to use a smaller resource class as I’m on the free plan and did get a warning about the image being deprecated.

version: 2.1
orbs:
  android: circleci/android@2.4.0

jobs:
  build_dev_app:
    executor:
      name: android/android-machine
      resource-class: large
      tag: 2022.09.1
    steps:
      - checkout            

workflows:
  build-and-test:
    jobs:
      - build_dev_app

The real problem is that the original post was made without considering the use of the ORB. So to use the ORB you set tag: to default or edge as in the following example

version: 2.1
orbs:
  android: circleci/android@2.4.0

jobs:
  build_dev_app:
    executor:
      name: android/android-machine
      resource-class: large
      tag: default
    steps:
      - checkout            

workflows:
  build-and-test:
    jobs:
      - build_dev_app
1 Like