... | @@ -25,7 +25,7 @@ Cognizant of costs and maintenance overhead, we categorize the environments to a |
... | @@ -25,7 +25,7 @@ Cognizant of costs and maintenance overhead, we categorize the environments to a |
|
* **Dev Secondary Environment**
|
|
* **Dev Secondary Environment**
|
|
* This is a proposed environment also linked to the community Gitlab CICD. This allows us to avoid a code freeze when the community reaches a milestone and to allow for parallel trusted builds to run for both the tagging/milestone builds in Dev2 and the mater branch MR builds in Dev primary. No platform level validation/integration tests are performed.
|
|
* This is a proposed environment also linked to the community Gitlab CICD. This allows us to avoid a code freeze when the community reaches a milestone and to allow for parallel trusted builds to run for both the tagging/milestone builds in Dev2 and the mater branch MR builds in Dev primary. No platform level validation/integration tests are performed.
|
|
|
|
|
|
* **QA Automation (aka "Platform Validation" Environment**
|
|
* **QA Automation (aka "Platform Validation") Environment**
|
|
* It is important for the community that the automated QA tests are done with a) real-world data sets (TNO, Volve, etc.) and b) with the representative deliverable they will receive from the provider/CSP own CICD. Note that the deployed environment does not pick up binaries from the milestone tagged version in community Gitlab, so the need to integrate the outputs from the provider/CSP CICD into the automated QA environment. Milestone releases should be pushed in here and all the integration (functional) tests will be run in an automated fashion here.
|
|
* It is important for the community that the automated QA tests are done with a) real-world data sets (TNO, Volve, etc.) and b) with the representative deliverable they will receive from the provider/CSP own CICD. Note that the deployed environment does not pick up binaries from the milestone tagged version in community Gitlab, so the need to integrate the outputs from the provider/CSP CICD into the automated QA environment. Milestone releases should be pushed in here and all the integration (functional) tests will be run in an automated fashion here.
|
|
|
|
|
|
* **Preship Production (Business UAT) Environment**
|
|
* **Preship Production (Business UAT) Environment**
|
... | | ... | |