Packages not installing on publisher

[stiegjo22]

We're having a problem with packages not installing on our AEM publisher. (we deploy via TeamCIty) The only recent change we've made is adding the following change to some of the pom.xml to set up our project for Adobe Cloud Manager. (we haven't migrated yet)

                    <properties>
                            <cloudManagerTarget>none</cloudManagerTarget>
                        </properties>

[arunpatidar]

Hi @stiegjo22 
The property does exactly the same, what you are facing.

https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/getting-started/pro... 

Cloud Manager will look for a property named cloudManagerTarget in the properties of built content packages. If this property is set to none, the package will be skipped and not deployed.

[stiegjo22]

Yes - I understand that it will skip in Cloud Manager if set to none. However we're still deploying to an on-premise instance of AEM and it's not installing on the publisher. Thanks.

[Sudheer_Sundalam]

@stiegjo22 ,

Based on the screenshot provided, I'm assuming you are using one of the latest archetypes. In your project, if you have 

"all" maven module, you need to set 

<cloudManagerTarget>all</cloudManagerTarget>

in the "all" maven module pom.xml file. 

Also, you need to have other maven modules like ui.apps, ui.config, and ui.content added in the embed section of filevault-package-maven-plugin configuration.

Both in Adobe CM & (I think on-premise), the <cloudManagerTarget>none</cloudManagerTarget> is set to none to avoid individual packages getting installed on their own. By installing "all" package, other embed packages are automatically installed.

[stiegjo22]

Thanks Sudheer. I do have this defined in my all pom.xml file:

       <properties>
                        <cloudManagerTarget>all</cloudManagerTarget>
                    </properties>

[Sudheer_Sundalam]

@stiegjo22 ,

I am not sure of how you are using TeamCity CI/CD to build and deploy the aem code to servers, just make sure you are uploading only all.zip file and installing the same through the CI/CD pipeline job.

I remember seeing this issue in my project where the packages gets uploaded but not installed. I simply installed them manually via package manager a couple of times, then it was all fine and packages were uploaded and installed as expected.

[aanchal-sikka · Accepted solution]

@stiegjo22 

We would also need to Embed the dependencies in all module. Just cloudManagerTarget would not suffice. Example:

 <embeddeds>
                        <embedded>
                            <groupId>com.adobe.aem.guides</groupId>
                            <artifactId>aem-guides-wknd.ui.apps</artifactId>
                            <type>zip</type>
                            <target>/apps/wknd-packages/application/install</target>
                        </embedded>
                        <embedded>
                            <groupId>com.adobe.aem.guides</groupId>
                            <artifactId>aem-guides-wknd.core</artifactId>
                            <target>/apps/wknd-packages/application/install</target>
                        </embedded>
                        <embedded>
                            <groupId>com.adobe.aem.guides</groupId>
                            <artifactId>aem-guides-wknd.ui.content</artifactId>
                            <type>zip</type>
                            <target>/apps/wknd-packages/content/install</target>
                        </embedded>
                        <embedded>
                            <groupId>com.adobe.aem.guides</groupId>
                            <artifactId>aem-guides-wknd.ui.config</artifactId>
                            <type>zip</type>
                            <target>/apps/wknd-packages/application/install</target>
                        </embedded>
                        <embedded>
                            <groupId>com.adobe.aem.guides</groupId>
                            <artifactId>aem-guides-wknd.ui.content.sample</artifactId>
                            <type>zip</type>
                            <target>/apps/wknd-packages/content/install</target>
                        </embedded>
                        <embedded>
                            <groupId>com.adobe.aem.guides</groupId>
                            <artifactId>aem-guides-wknd-shared.ui.content</artifactId>
                            <type>zip</type>
                            <target>/apps/wknd-vendor-packages/content/install</target>
                        </embedded>
                    </embeddeds>

So, all the packages would be embedded into all module and all would be deployed. The other modules which are part of all will then be picked by AEM and installed.

Sample pom.xml of all : https://github.com/adobe/aem-guides-wknd/blob/main/all/pom.xml

[stiegjo22]

Thank you.