Loading

Existing Pipelines errors with ANT Migration Tool in CI/CD DevOps Tools After Summer ’26 Field Introduction

Publish Date: May 15, 2026
Description
After the Summer ’26 release, deployments or validations using the ANT Migration Tool may fail during Apex test execution retrieval.

Salesforce introduced the following new fields on the ApexTestResult object in API version 65.0:

  • TestCategory
  • TestName
  • TestNamespace

These fields were added to the Tooling API and documented in the Tooling API Reference Guide.
As a result, existing CI/CD pipelines that still rely on the deprecated ANT Migration Tool may encounter XML parsing failures similar to the following:

[sf:deploy] Failed to check the status for request ID=0Afxxxxxxxxxxx.
Error: unable to find end tag at:
START_TAG seen ...<namespace xsi:nil="true"/><testCategory xsi:nil="true"/>...
@8841:29076. Retrying...

This issue occurs because the ANT Migration Tool is no longer maintained and does not support newer metadata/API changes introduced in recent Salesforce releases.

Cause:

The ANT Migration Tool reached End of Life (EOL) and is no longer supported or maintained by Salesforce. Due to the lack of ongoing updates, the tool is incompatible with newer API changes introduced in Summer ’26, including the additional fields on the ApexTestResult object.


Resolution
Salesforce recommends migrating existing CI/CD pipelines from the ANT Migration Tool to the Salesforce CLI (sf CLI).

The sf CLI is the supported deployment and DevOps solution and is actively maintained to support the latest Salesforce platform changes and API versions.

Recommended Actions
  • Replace ANT-based deployment commands with sf CLI commands.
  • Update CI/CD automation scripts and DevOps pipelines accordingly.
  • Ensure pipelines use supported Salesforce CLI versions and API versions.

Example deployment command using sf CLI:

sf project deploy start --source-dir force-app

Additional Resources
Knowledge Article Number

005360282

 
Loading
Salesforce Help | Article