Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Summit 2023 [19th to 23rd March, Las Vegas and Virtual] | Complete AEM Session & Lab list
SOLVED

AEMCaaS: Pipeline, how to change the Adobe build scripts for pipelines?

Avatar

Level 5

For AEMCaas, how do we change the Adobe build scripts for pipelines?

What happens if I want to do something like
mvn clean -PautoInstallPackage -DversionOfMyService=1.0.0 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

You cannot change the CM pipeline. It is designed to have a single predictive flow so that we can have consistent results. There are two ways you can extend your CM pipelines.

 

1. Using cloud manager API. You can hook into events/steps specified using the API (reference at [1]) and build custom actions in your system

2. Custom pipelines in customer git before merging into Adobe Git repo. - have own pipelines and the final step is merging up to Adobe Git (of course its an overhead, but different organisations has different requirements)

0 Replies

Avatar

Employee

Hi @AEMWizard ,

 

You cannot change the maven command on Cloud manager, if there is any need for inclusion/exclusion you can use pom.xml for that.

 

Hope that helps!

 

Regards,

Nitesh

Avatar

Community Advisor

There is no provision to add the maven command directly in cloud manager for CI/CD pipeline , they are pre-configured with standards .

You can check with adobe support team if there is something specific for your program.

 

Ref: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

 

 

 

Avatar

Correct answer by
Employee Advisor

You cannot change the CM pipeline. It is designed to have a single predictive flow so that we can have consistent results. There are two ways you can extend your CM pipelines.

 

1. Using cloud manager API. You can hook into events/steps specified using the API (reference at [1]) and build custom actions in your system

2. Custom pipelines in customer git before merging into Adobe Git repo. - have own pipelines and the final step is merging up to Adobe Git (of course its an overhead, but different organisations has different requirements)