We are working to move towards Cloud Manager for our CI/CD.
We are using process mentioned here:
https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/developing/aem-...
But although I am keeping the zip content packages under "install" folder, in Stage it is only deploying in Publishers but not installing in Author.
Package deploys fine in both Auth and Publish in Dev and QA which have single Auth and single Pub.
Stage have 1 Auth and 2 Pubs.
Any pointer..?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
Is your master branch has the same POM as non prod POM?
Can you also check if the package is getting copied or not in Stage?
Hi,
Is your master branch has the same POM as non prod POM?
Can you also check if the package is getting copied or not in Stage?
Hi @Mayukh001
Could you also please check on ACL's missing if any(since you've mentioned content packages) along with what @arunpatidar mentioned.
we have the same issue as well. The package ui.apps and ui.content are uploaded to publish instances but NOT INSTALLED. but this is not happening in QA environment and prod. Untill last release it started happening in production as well. we even raised an adobe support ticket, not much help from them. Could you please let me know how did you resolve.
note:
we are using cloud manager non-production pipeline to build and deploy on stage. The Stage environment is non-production for us and we have preprod and prod as part of production pipeline.
We are using 0.0.1-SNAPSHOT in the pom. We didn't want to maintain any versions
project created based on maven archetype 33
Hi,
Did you solve your issue ? We are facing the same thing on AEM 6.5 : we use the "Production pipeline" on Cloud Manager to build and deploy on STAGE (1 author, 2 publish), and packages are uploaded but not installed on Author and Publish. We have the message "A different version is installed" that references the version before the deployment.
Thank you
is this resolved for you?
Views
Likes
Replies
Views
Likes
Replies