Hello
We are deprecating the following Android images on CircleCI and will be removing them from our platform on Sept 30, 2024:
Tags:
- android:202102-01
- android:2021.12.1
- android:2022.01.1
- android:2022.03.1
- android:2022.04.1
- android:2022.06.1
- android:2022.06.2
- android:2022.07.1
- android:2022.08.1
- android:2022.09.1
- android:2023.03.1
- android:2023.04.1
- android:2023.06.1
- android:2023.07.1
- android:2023.09.1
- android:2023.11.1
Once an image is removed, the CircleCI jobs that use that image will fail with an error message - This job was rejected because the image is unavailable .
CircleCI will email impacted users with a list of projects that must be updated before the EOL date.
Why are these images being deprecated?
To ensure pipelines on CircleCI run with the highest level of reliability & security.
What do I need to do if my build shows a “deprecated image” banner?
The changes you will need to make depend on how you are specifying your image choice.
Changes necessary if you are not using the Android orb
You will need to update your CircleCI config to use a valid Android image as per the tagging conventions in our Android Image Policy.
The recommended tags to use are as follows:
default
- latest stable version and version if do not specify anythingedge
- Development image of latest image
A couple examples:
Before:
machine:
image: android:202102-01 // any of the deprecated image tags above
After:
machine:
image: android:default
machine:
image: android:edge
Changes necessary if you are using the Android orb
Users of the Android Orb version 2.0.0 or later you will only see a deprecated image they have explicitly specified the tag of such an image in your build (users of Android orbs prior to version 2.0.0 are encouraged to upgrade).
You will need to update your CircleCI config to either use the default Android image (by removing the explicit tag:
in the config) or changing the config (by altering the tag:
value) to use a valid Android image as per the tagging conventions in our Android Image Policy.
An example:
Before:
version: '2.1'
orbs:
android: circleci/android@2.5.0
jobs:
test:
executor:
name: android/android-machine
tag: 202102-01
steps:
...
After:
version: '2.1'
orbs:
android: circleci/android@2.5.0
jobs:
test:
executor:
name: android/android-machine
steps:
...
What will happen after the Sept 30 EOL Date?
If you do not currently specify an image, your job will keep the same behavior, and use the default
tag automatically.
Calling any of the deprecated image tag versions directly will cause your job to fail.
Brownout Schedule and EOL
We will be conducting brownouts for the above images on the following dates and times.
- 25 March 2024
- 07:00 UTC → 11:00 UTC
- 13:00 UTC → 17:00 UTC
- 20:00 UTC → 00:00 UTC
- 25 June 2024
- 01:00 UTC → 11:00 UTC
- 13:00 UTC → 23:00 UTC
- 18 September 2024
- 00:00 UTC → 00:00 UTC (24 Hour)
- 30 September 2024
- Deprecated tags are removed and will be unavailable
During these times, all jobs calling these images will fail. Please update your configs as soon as possible to prevent any disruption to your pipelines.
The default
tag is available for you to transition to as of writing and we highly recommend updating your config to avoid job failure during these brownouts. If you have already updated your tags, please disregard this email.
What’s Next?
Details on how we manage and maintain our Android images can be found here: Android Image Policy.
Feedback
If you have any questions, comments, or concerns, please post a reply in this thread and we will be happy to help!
Respectfully,
CircleCI Images Team