Custom CI/CD for AMS | Community
Skip to main content
RajaShankar
RajaShankar
New Participant
November 26, 2022
Solved

Custom CI/CD for AMS

  • November 26, 2022
  • 1 reply
  • 762 views

Hi All,

We are Adobe AEM 6.5 AMS. We are currently doing manual deployment with packages in non prod and prod.Due to various security reason in organization we are unable to move the code to Cloud Manager.Now how can we automate the CI/Cd process without Cloud Manager in AMS model. 

 

Alternatively we have in house Ci/CD frameworks(Jenkins based).Can we use that to automate the CI/CD. Does Adobe allows to deploy to prod publisher in AMS from in house CI/CD .Problem is currently Adobe AMS dont share password of prod pub.In that case how do we execute CLI from Jenkins (Note: Non prod and Prod direct author /dispatcher url's are already whitelisted within organization)

 

Any suggestion will be helpful.

 

Regards

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 Avinash_Gupta_

Hi @rajashankar 

 

Recommendation would be to use cloud manager and discuss all your security reasons with AMS team and they will surely sort it out .

 

In case you want to leverage inhouse Jenkins for CI/CD build, it would be possible for all non prod environments but based on my experience with AMS, they won't prefer to do any builds on PROD environment except cloud manager. Deploying packages through CI/CD pipeline sometimes brings the entire instance down and AMS don't want to take the risk as it's a PROD environment. For PROD deployment, usually they would choose the deployed packages from Staging/Non prod environments which are the closet replica of PROD and where the codes changes are thoroughly tested.

 

Also, for the security reasons AMS won't share the PROD Publisher credentials as these credentials need to be setup on the Jenkins and in case person who has the access of Jenkins pipeline can easily get the credentials of PROD.

 

Talk to your AMS representative and surely they will provide you a solution. Hope this helps. 

1 reply

Avinash_Gupta_
Avinash_Gupta_Accepted solution
New Participant
November 27, 2022

Hi @rajashankar 

 

Recommendation would be to use cloud manager and discuss all your security reasons with AMS team and they will surely sort it out .

 

In case you want to leverage inhouse Jenkins for CI/CD build, it would be possible for all non prod environments but based on my experience with AMS, they won't prefer to do any builds on PROD environment except cloud manager. Deploying packages through CI/CD pipeline sometimes brings the entire instance down and AMS don't want to take the risk as it's a PROD environment. For PROD deployment, usually they would choose the deployed packages from Staging/Non prod environments which are the closet replica of PROD and where the codes changes are thoroughly tested.

 

Also, for the security reasons AMS won't share the PROD Publisher credentials as these credentials need to be setup on the Jenkins and in case person who has the access of Jenkins pipeline can easily get the credentials of PROD.

 

Talk to your AMS representative and surely they will provide you a solution. Hope this helps. 

    Terms & ConditionsAccessibility statement

    Loading footer...