AndroidBuild@1 is retired: replace it with Gradle@4
The short answer
- Retirement date
- Removal date
- . Pipelines that still use it fail after removal.
- Replacement
Gradle@4- Kind of migration
- manual migration
- Automatic rewrite
- No. This task needs a manual migration. trasloco modernize --check still finds the step.
- Recommended action
- Migrate this step manually to Gradle@4, reviewing the documented behavior and input differences.
Official sources
- Official task retirement announcement
- Task definition: AndroidBuild (task.json)
- Task definition: GradleV4 (task.json)
Last verified:
Why does my pipeline show a retirement error for AndroidBuild@1?
On , Azure Pipelines shows a retirement error for AndroidBuild@1, but the run does not fail. On , pipelines that still use AndroidBuild@1 fail.
Find it in your pipelines
With trasloco:
trasloco modernize --check
Install trasloco from the latest release.
With plain grep, nothing to install:
grep -rniwF 'AndroidBuild@1' --include='*.yml' --include='*.yaml' .
How to migrate
Migrate this step manually to Gradle@4, reviewing the documented behavior and input differences.
The task definition of the replacement is linked under official sources above.
AndroidBuild@1 retirement FAQ
Is AndroidBuild@1 deprecated?
Yes. AndroidBuild@1 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.
When does AndroidBuild@1 stop working?
AndroidBuild@1 is removed on 2027-03-15. Pipelines that still use it fail after removal.
What should I use instead of AndroidBuild@1?
Replace AndroidBuild@1 with Gradle@4.
Related retired tasks
- AndroidSigning@1 — manual migration
- AndroidSigning@2 — manual migration
- AzureCLI@0 — manual migration
- AzureMonitor@0 — manual migration
- AzureNLBManagement@1 — manual migration
- Gradle@1 — replacement with input changes