Pipeline validation failures due to deprecated testing client library cloud pipelines

In Adobe Experience Manager as a Cloud Service, pipeline validations fail when projects reference deprecated versions of the aem-cloud-testing-clients library. Outdated dependencies remain in test modules, unused components, or older branches and trigger warnings or failures during the Custom Functional Testing stage. To fix this issue, update all references to supported versions or remove the dependency if it is not used

Description description

Environment

  • Adobe Experience Manager as a Cloud Service(AEMaaCS)
  • Adobe Experience Manager Assets

Issue/Symptoms

  • Proactive notification emails with subjects such as Your AEM project is using a Deprecated Version of aem-cloud-testing-clients — Upgrade Needed
  • Pipeline failures or warnings during the Custom Functional Testing step after infrastructure updates
  • Dependency incompatibility warnings referencing deprecated versions of aem-cloud-testing-clients
  • Repeated alerts even when the library is not actively used due to outdated references in it.tests/pom.xml, stale branches, or unused modules

Cause

One or more pom.xml files in the project use an outdated version of aem-cloud-testing-clients (below 1.2.1). These versions are not compatible with Cloud Manager updates and can cause warnings or failures during Custom Functional Testing. Cloud Manager scans all modules and branches, so it still detects these outdated references even if they are not actively used.

Resolution resolution

To fix this issue, follow these steps:

  1. Search the entire project repository for all references to aem-cloud-testing-clients by using your IDE or running grep -r "aem-cloud-testing-clients" from the project root.
  2. Update the dependency in every pom.xml file to version 1.2.1 or later. Use the latest available versions such as 1.2.9 or 1.3.0.
  3. Remove the aem-cloud-testing-clients dependency if the project does not use custom functional tests.
  4. Commit the changes to the repository and run a full Cloud Manager pipeline.
  5. Rerun pipelines for all environments such as Dev, Stage, Prod, and Sandbox so Cloud Manager rescans the updated code and clears any existing detection flags.

Note

Contact Adobe Support if warnings continue after fixes. Share modules, commit hashes, pipeline URLs, and search results for aem-cloud-testing-clients.

recommendation-more-help
experience-cloud-kcs-help-kbarticles