Looking for guidance/tips on how to setup a DevOps CI/CD pipeline(s) via EDS | Community
Skip to main content
Saad-A
Saad-A
Level 2
January 29, 2025
Solved

Looking for guidance/tips on how to setup a DevOps CI/CD pipeline(s) via EDS

  • January 29, 2025
  • 3 replies
  • 682 views

Hey Everyone,

 

Context: Our team is currently trying to optimally setup a client's project, and we want to create a smooth CI/CD system which will take into account both the development side of contributions as well as the actual content authoring side (client side) of the flow.

 

The tooling and process we're utilizing is as such (see attached screenshot as well of our current infra thinking & layout):

- Document/Content Authoring & Asset Management = Sharepoint

- Version Control and Development Organization = GitHub

- Deployment and CDN = AEMaaCS (were using Edge Delivery)

 

As for utmost safety in a project and to prevent unwanted mistakes, multiple environments should exist ideally. But so far this is understood by our team as such:

- Feature branches take in local code changes/pushes

- Merge into a Staging branch

- Merge into QA or Main from which it goes to a production pipeline

- The pipeline is triggered from main

- Pipeline deploys to production (.com) site directly from .live (published content)

- Content authors can now see the changes on the main site, and choose to make changes

 

What we want to know is:

  • How to setup the different environments in the Edge Delivery Solution, considering we can only add EDS domains?
    • Do we set up separate domains (staging.abc.com for example) for each environment?
    • Would having multiple domains or subdomains be a good approach?
    • Is it necessary when working with an EDS process? Is a staging environment even needed?
  • How do we bifurcate/manage content and page differences between QA and Staging environments? Do we need different Sharepoint mount URLs?
  • Can SharePoint's version history fully address rollback scenarios, especially for deleted content in production?
  • What specific measures (e.g., robots.txt, meta tags) can be implemented to ensure non-production environments are excluded from search engine crawling?

Not all questions need to be addressed, just providing context for where we are stuck - seeking advice or tips on the best approach. 

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 AshwiniSathe1

Hi @saad-a.

I had worked on EDS with document based authoring for one of our client. We did followed some procedures which can answer few of your questions.

1. Separate repo for each environment: we created separate github repositories for each environment and added workflow to push the changes automatically to higher env repo.

2. Separate mount URL/ SharePoint path: we created separate SharePoint paths for each env and those are mapped to mount URL in respective github repos.

3. CI/CD pipeline: With cloud manager, we created private repository pointing to client github repo and generate secret code which needs to be added to the github repo in /well-known/adobe/cloudmanager-challenge.txt file. This will automate the pipeline with the client github repository.

 

Thanks

3 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
February 3, 2025

@aanchal-sikka@gkalyan@briankasingli@heenamadan@saumya@martin_ecx_io@chitramadan@narendiran_ravi@asutosh_jena_

@rajumuddana

Kindly take a moment to review this question and share your valuable insights. Your expertise would be greatly appreciated!

Kautuk Sahni
AshwiniSathe1
AshwiniSathe1Accepted solution
Level 3
February 6, 2025

Hi @saad-a.

I had worked on EDS with document based authoring for one of our client. We did followed some procedures which can answer few of your questions.

1. Separate repo for each environment: we created separate github repositories for each environment and added workflow to push the changes automatically to higher env repo.

2. Separate mount URL/ SharePoint path: we created separate SharePoint paths for each env and those are mapped to mount URL in respective github repos.

3. CI/CD pipeline: With cloud manager, we created private repository pointing to client github repo and generate secret code which needs to be added to the github repo in /well-known/adobe/cloudmanager-challenge.txt file. This will automate the pipeline with the client github repository.

 

Thanks

    narendiran_ravi
    narendiran_ravi
    Level 6
    February 8, 2025
    • We don't need any specific settings to exclude nonprod content from crawling. By default, EDS will not index any content from *.aem.live or *.aem.page by loading default robots.txt with the config below. 
    User-agent: *
Disallow: /
    •  Separate branches can be used for different environments
      Terms & ConditionsAccessibility statement

      Loading footer...