CloudManager: Build did not produce any non-skipped content package artifacts | Community
Skip to main content
J
jamiec4451712
Level 3
October 20, 2022
Solved

CloudManager: Build did not produce any non-skipped content package artifacts

  • October 20, 2022
  • 1 reply
  • 1817 views

I am getting this error with my CloudManager build. The build succeeds, and I am definitely generating a content package. I have triple checked my pom files and compared against the latest archetype and I can't really see anything I can change.

 

The error reads:

Build did not produce any non-skipped content package artifacts. At least one non-skipped content package is required for AEM Cloud Service builds.

 

It would be great to get a description from Adobe about precisely what this requirement is. ie. what is the code that throws this error looking for? A specific package in a specific folder? Or a file with a specific value somewhere?

 

Any help is greatly appreciated!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by jamiec4451712

Hi LokeshVajrala,

 

Your comment helped me track down the answer. The line:

<cloudManagerTarget>none</cloudManagerTarget>


Got put in the root pom, which was then inherited by the child pom. For anyone with this issue in the future, it helps to check the properties.xml that gets generated with the build (ex. target/vault-work/META-INF/vault/properties.xml) to make sure you don't see a line line this:

 

<entry key="cloudManagerTarget">none</entry>

 

For your "all" package.

 

Thank you!

1 reply

Lokesh_Vajrala
Community Advisor
Lokesh_VajralaCommunity Advisor
Community Advisor
October 20, 2022

Hi @jamiec4451712 

 

Check your project modules pom.xml files have correct packageType mentioned as per the documentation - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/aem-project-content-package-structure.html?lang=en#xml-package-types 

 

And next check this section - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/aem-project-content-package-structure.html?lang=en#cloud-manager-target (I'm guessing you might be missing this section)

Marking Packages for Adobe Cloud Manager Deployment

In every project generating a Package, except for the container (all) project, add <cloudManagerTarget>none</cloudManagerTarget> to the <properties> configuration of the filevault-package-maven-plugin plug-in declaration to ensure they are not deployed by Adobe Cloud Manager. The container (all) package should be the singular package deployed via Cloud Manager, which in turn embeds all required code and content packages.

 

    J
    jamiec4451712AuthorAccepted solution
    Level 3
    October 20, 2022

    Hi LokeshVajrala,

     

    Your comment helped me track down the answer. The line:

    <cloudManagerTarget>none</cloudManagerTarget>


    Got put in the root pom, which was then inherited by the child pom. For anyone with this issue in the future, it helps to check the properties.xml that gets generated with the build (ex. target/vault-work/META-INF/vault/properties.xml) to make sure you don't see a line line this:

     

    <entry key="cloudManagerTarget">none</entry>

     

    For your "all" package.

     

    Thank you!

      Terms & ConditionsAccessibility statement

      Loading footer...