SOLVED
Using Adobe Cloud Manager – CI/CD Production and Non-Production Pipeline
1 Accepted Solution
Correct answer by
Why Separate Pipelines?
1. Development Stages: Development typically goes through stages, from development to testing, and finally to production. Non-production pipelines are used for development environments, where new features and bug fixes are developed and tested. Production pipelines, on the other hand, are used to deploy verified code to stage and then live environment where your end-users interact with your application.
2. Safety and Stability: By separating these pipelines, you minimize the risk of accidentally deploying untested or unstable code to your live production environment. This separation acts as a safeguard, ensuring that only thoroughly tested and reviewed code makes it to production.
3. Workflow and Approvals: The approval process for deploying to production is often more stringent, requiring multiple checks and sign-offs from stakeholders. Non-production deployments may have a more streamlined process since the primary aim is rapid development and testing.
Differences Between the Two Pipelines
- Purpose: Non-production is for development, testing, and staging. Production is for deploying to the live environment.
- Configuration: Different settings for security, performance, and debugging. Example Experience Audit testing is generally configured on Prod pipeline. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi...
- Approval Process: Production deployments typically have a more rigorous approval process.
Aanchal Sikka
Correct answer by
Why Separate Pipelines?
1. Development Stages: Development typically goes through stages, from development to testing, and finally to production. Non-production pipelines are used for development environments, where new features and bug fixes are developed and tested. Production pipelines, on the other hand, are used to deploy verified code to stage and then live environment where your end-users interact with your application.
2. Safety and Stability: By separating these pipelines, you minimize the risk of accidentally deploying untested or unstable code to your live production environment. This separation acts as a safeguard, ensuring that only thoroughly tested and reviewed code makes it to production.
3. Workflow and Approvals: The approval process for deploying to production is often more stringent, requiring multiple checks and sign-offs from stakeholders. Non-production deployments may have a more streamlined process since the primary aim is rapid development and testing.
Differences Between the Two Pipelines
- Purpose: Non-production is for development, testing, and staging. Production is for deploying to the live environment.
- Configuration: Different settings for security, performance, and debugging. Example Experience Audit testing is generally configured on Prod pipeline. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi...
- Approval Process: Production deployments typically have a more rigorous approval process.
Aanchal Sikka
