PrivateEdition/Current/PEGuide/SetCICDPipeline - Revision history

WikiSysop at 07:00, May 23, 2024

2024-05-23T07:00:31Z

WikiSysop at 14:32, October 27, 2022

2022-10-27T14:32:01Z

Ed.jamer@genesys.com: Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

2021-11-09T21:12:49Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:29:59Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Uma.jayakumar@genesys.com: Published

2021-07-09T17:32:53Z

Published

Uma.jayakumar@genesys.com: Published

2021-06-30T18:51:15Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Setting up a CD pipeline
|Context=Provides recommendations on setting up a Continuous Deployment (CD) pipeline in a your cloud private edition infrastructure for automated deployments.
|ComingSoon=No
|Section={{Section
|sectionHeading=CD Pipeline for Genesys Engage cloud private edition
|alignment=Vertical
|structuredtext=Genesys delivers its artifacts in the JFrog Artifactory Edge repository. You can pull the containers from JFrog and push it into your pipeline stream for automated deployments. Genesys strongly recommends automating deployments for its services via a CD pipeline. Genesys has no specific requirements for how the pipeline needs to be set up or what tools need to be employed to implement it.

Here is a quick overview of the steps involved in a typical CD environment.

#Download a container from the [https://pureengageuse1.jfrog.io/ui/login/ JFrog Artifactory Edge] repository.
#Push the downloaded container into your internal container registry or to a quarantine location for security scans.
#Perform security scans on the container.
#If you are confident with the scan results, promote the container to a test/pre-production environment.
#In the test/pre-production environment, upgrade the container by referring the upgrade procedure of the specific service in its service-level documentation. You can also check out the high level {{Link-SomewhereInThisVersion|manual=PEGuide|topic=UpgradProcess|display text=upgrade procedure}} in this guide.
#Test the updated environment by running the automated tests.
#Once the test results are satisfying, promote the container to the next environment (if applicable to your organization) for further validation before moving to production. {{NoteFormat|Your organization might have different environments other than the pre-production environment in order to test a new version of a container rigorously. Therefore, promoting a container to the next environment could mean a different environment for some users and production environment for other users.|}}
#Upgrade the container in the production environment by referring the upgrade procedure of the specific service in its service-level documentation. If you encounter any issue with the upgrade, you can always rollback to the previous point before the upgrade by referring the upgrade procedure of the specific service in its service-level documentation. You can also check out the high level {{Link-SomewhereInThisVersion|manual=PEGuide|topic=RollBack|display text=rollback procedure}} in this guide.

==Frequently asked questions==
The following FAQs answer important considerations when you are planning your CI/CI pipeline.
===What repository will Genesys use to provide Helm charts to customers?===
Genesys will provide continuous delivery updates in the [https://pureengageuse1.jfrog.io/ui/login/ JFrog Artifactory Edge] repository used for the initial deployment, as described in {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ManageServices}}.

===How many Helm charts are packaged for a Genesys Engage service?===
Genesys typically packages one Helm chart per service. However, for specific services like Genesys Web Services (GWS), you can use the same Helm chart and deploy different services by varying the values in the Helm chart.

===How do you solve dependencies between different Genesys components during deployment?===
During initial deployment, we enforce a specific {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ContDepOrder|display text=deployment order}} to be followed when you deploy Genesys Engage services. This will resolve the requirements on dependencies between different services. Once your initial deployment is up and running, you can upgrade individual services at different times.

We recommend you create a platform level CD pipeline to perform initial deployment in the required order.

===Will introducing a new component or Helm parameter affect the existing ecosystem of services?===
No. You can deploy the new service by following its instructions provided the core components like GAuth, GWS, Tenant service, etc. are already deployed.
|Status=No
}}
}}

@@ Line 15: / Line 15: @@
 Here is a quick overview of the pipeline steps involved in a typical CD environment.
-#Download a container from the [https://pureengageuse1.jfrog.io/ui/login/ JFrog Artifactory Edge] repository.
+#Download a container from the Genesys repository.
 #Push the downloaded container into your internal container registry or to a quarantine location for security scans.
 #Perform security scans on the container.
@@ Line 41: / Line 41: @@
 {{NoteFormat|For additional information on pipelines and examples, refer to the [https://github.com/genesys/multicloud-services/ Private Edition] page in our public repository.}}
 |Status=No
 }}
 }}

@@ Line 39: / Line 39: @@
 ===Will introducing a new component or Helm parameter affect the existing ecosystem of services?===
 No. You can deploy the new service by following its instructions provided the core components like GAuth, GWS, Tenant service, etc. are already deployed.
 |Status=No
 }}
 }}

@@ Line 29: / Line 29: @@
 Genesys will provide continuous delivery updates in the [https://pureengageuse1.jfrog.io/ui/login/ JFrog Artifactory Edge] repository used for the initial deployment, as described in {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ManageServices}}.
-===How many Helm charts are packaged for a Genesys Engage service?===
+===How many Helm charts are packaged for a Genesys Multicloud CX service?===
 Genesys typically packages one Helm chart per service. However, for specific services like Genesys Web Services (GWS), you can use the same Helm chart and deploy different services by varying the values in the Helm chart.
 ===How do you solve dependencies between different Genesys components during deployment?===
-During initial deployment, we enforce a specific {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ContDepOrder|display text=deployment order}} to be followed when you deploy Genesys Engage services. This will resolve the requirements on dependencies between different services. Once your initial deployment is up and running, you can upgrade individual services at different times.
+During initial deployment, we enforce a specific {{Link-SomewhereInThisVersion|manual=PEGuide|topic=ContDepOrder|display text=deployment order}} to be followed when you deploy Genesys Multicloud CX services. This will resolve the requirements on dependencies between different services. Once your initial deployment is up and running, you can upgrade individual services at different times.
 We recommend you create a platform level CD pipeline to perform initial deployment in the required order.

@@ Line 5: / Line 5: @@
 |ComingSoon=No
 |Section={{Section
-|sectionHeading=CD Pipeline for Genesys Engage cloud private edition
+|sectionHeading=CD Pipeline for Genesys Multicloud CX private edition
 |alignment=Vertical
 |structuredtext=Genesys delivers its artifacts in the JFrog Artifactory Edge repository. You can pull the containers from JFrog and push it into your pipeline stream for automated deployments. Genesys strongly recommends automating deployments for its services via a CD pipeline.