Cloud Manager FAQs cloud-manager-faqs
This document provides answers to the most frequently asked questions about Cloud Manager for AMS customers.
Is it possible to use Java 11 with Cloud Manager builds? java-11
Yes. You need to add the maven-toolchains-plugin with the correct settings for Java 11.
- This process is documented here.
- For an example, see the WKND sample project code.
My build fails with an error about maven-scr-plugin after switching from Java 8 to Java 11. What can I do? maven-src-plugin
Your AEM Cloud Manager build may fail when attempting to switch the build from Java 8 to 11. If you encounter the following error, then you need to remove maven-scr-plugin and convert all OSGi annotations to OSGi R6 annotations.
[main] [ERROR] Failed to execute goal org.apache.felix:maven-scr-plugin:1.26.4:scr (generate-scr-scrdescriptor) on project helloworld.core: /build_root/build/testsite/src/main/java/com/adobe/HelloWorldServiceImpl.java : Unable to load compiled class: com.adobe.HelloWorldServiceImpl: com/adobe/HelloWorldServiceImpl has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 -> [Help 1]
For instructions on how to remove this plug-in, see here.
My build fails with an error about RequireJavaVersion after switching from Java 8 to Java 11. What can I do? requirejavaversion
For Cloud Manager builds, the maven-enforcer-plugin may fail with this error
[main] [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion
This known issue is due to Cloud Manager using a different version of Java to run the Maven command versus compiling code. Omit requireJavaVersion from your maven-enforcer-plugin configurations.
The code quality check failed and now deployment is stuck. Is there a way to bypass this check? deployment-stuck
Yes. All code quality failures, except for security ratings, are non-critical metrics. As such, they can be bypassed as part of a deployment pipeline by expanding the items in the results UI.
A user with the Deployment Manager, Project Manager, or Business Owner role can override the issues. In such a case, the pipeline proceeds. Or, they can accept the issues, in which case the pipeline stops with a failure.
See the documents Three-Tier Gates while Running a Pipeline and Configuring Non-Production Pipelines for more details.
Cloud Manager deployments fail at the performance test step in Adobe Managed Services environments. How can this issue be debugged to pass the critical metrics? debug-critical-metrics
There is no single answer to this question. However, you may find the following points about the performance test step helpful:
- This step is a web performance step. That is, it is about the time to load the page using a web browser.
- The URLs listed in the result .csv file are loaded in a Chrome browser in the Cloud Manager infrastructure during the test.
- A common metric that fails is the error rate. So, for a URL to pass, the main URL must load with
200status and in less than20seconds. If a page load exceeds20seconds, it is marked as a504error. - If your site requires user authentication, see Understand Your Test Results for configuring the test so you can authenticate to your site.
See Understanding Test Results for more information about quality checks.
Can I use SNAPSHOT for the version of the Maven project? snapshot
Yes. For developer deployments, the Git branch pom.xml files must contain -SNAPSHOT at the end of the <version> value.
Doing so lets subsequent deployments still be installed when the version did not change. In developer deployments, no automatic version is added or generated for the maven build.
You can also set the version to -SNAPSHOT for stage and production builds or deployments. Cloud Manager automatically sets a proper version number and creates a tag for you in Git. This tag can be referred to later, if required.
Further details about version handling are documented here.
How does package and bundle versioning work for staging and production deployments? staging-production
In staging and production deployments, an automatic version is generated as documented here.
For custom versioning in stage and production deployments, set a proper three-part maven version like 1.0.0. Increase the version each time you deploy to production.
Cloud Manager automatically adds its version to stage and production builds and creates a Git branch. No special configuration is required. If you do not set a maven version as described previously, the deployment still succeeds and a version is automatically set.
My maven build fails for Cloud Manager deployments but it builds locally without errors. What is wrong? maven-build-fail
See this Git resource for more details.
I am unable to set a variable using an aio command. What can I do? set-variable
You may receive a 403 error such as the following when attempting to list or set pipeline variables via aio commands.
$ aio cloudmanager:list-pipeline-variables 222
Cannot get variables: https://cloudmanager.adobe.io/api/program/111/pipeline/222/variables (403 Forbidden)
$ aio cloudmanager:set-pipeline-variables 222 --variable TEST 1
Cannot get variables: https://cloudmanager.adobe.io/api/program/111/pipeline/222/variables (403 Forbidden)
$ aio cloudmanager:set-environment-variables 1755 --variable TEST 1
setting variables... !
Cannot set variables: https://cloudmanager.adobe.io/api/program/111/environment/222/variables (403 Forbidden)
In this case, the user executing these commands needs to be added to the Deployment Manager role in the Admin Console.
See API Permissions for more details.