Gradle@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
- replacement with input changes
- Automatic rewrite
- Not yet. Automatic rewrite is planned for this kind of task (replacement with input changes). Today, trasloco modernize --check finds the step and you change it by hand.
- Recommended action
- Replace Gradle@1 with Gradle@4 and review the replacement inputs before updating the pipeline.
Official sources
- Official task retirement announcement
- Task definition: Gradle (task.json)
- Task definition: GradleV4 (task.json)
Last verified:
Why does my pipeline show a retirement error for Gradle@1?
On , Azure Pipelines shows a retirement error for Gradle@1, but the run does not fail. On , pipelines that still use Gradle@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 'Gradle@1' --include='*.yml' --include='*.yaml' .
How to migrate
Replace Gradle@1 with Gradle@4 and review the replacement inputs before updating the pipeline.
The task definition of the replacement is linked under official sources above.
Gradle@1 retirement FAQ
Is Gradle@1 deprecated?
Yes. Gradle@1 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.
When does Gradle@1 stop working?
Gradle@1 is removed on 2027-03-15. Pipelines that still use it fail after removal.
What should I use instead of Gradle@1?
Replace Gradle@1 with Gradle@4.
Related retired tasks
- AndroidBuild@1 — manual migration
- ArchiveFiles@1 — replacement with input changes
- AzureFunction@0 — replacement with input changes
- CacheBeta@0 — replacement with input changes
- cURLUploader@1 — replacement with input changes
- DotNetCoreCLI@0 — replacement with input changes