Pipeline failure of product functional Test

[RebinR1]

We’ve set up a development environment and configured a pipeline to connect the Adobe repository to it. However, before cloning the repository or making any changes to it, I tried starting the pipeline—and it failed. What could be the possible reasons for this failure?

[narendiran_ravi]

Hi @RebinR1 ,

Could you provide more details? Was your build successful locally? At which step did the pipeline fail? You can download the logs from the pipeline to check for errors.

[aanchal-sikka]

@RebinR1 

Please share the error messages from the logs of the pipeline

[SantoshSai]

Hi @RebinR1,

Have you checked if your Git Repository is empty? Most probably:

• If your Adobe Git repo is empty or lacks required files (pom.xml, ui.apps, ui.content, etc.), the build step will fail.

• Cloud Manager expects a Maven project structure and necessary AEM module folders.

Try cloning the Adobe repository and verify if everything is in place as required, also, worth to validate that your pipeline is mapped to the correct environment.

Appreciate if you provide the exact error message or log you see when the pipeline fails.

[EstebanBustamante · Accepted solution]

Hi @RebinR1 

Product Functional Tests are managed by Adobe. If they’re failing, it’s best to raise a support ticket with Adobe. That said, these tests can sometimes fail due to odd or temporary conditions, but often pass when you rerun the pipeline. Have you noticed this happening consistently?

Learn more here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi... 

Hope this helps

[kautuk_sahni]

@RebinR1 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!