What's new in Customer Journeys?

Connect and learn more! ×
B2C Service Customisations CI/CD Process — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

B2C Service Customisations CI/CD Process

Received Response
523
Views
10
Comments
edited May 31, 2023 1:48PM in General Technical Discussions 10 comments

CI/CD based automated development process envisages faster and frequent delivery of software features to live production.

  • With Continuous Integration (CI), code could be automatically checked for coding violations and unit tests coverage thresholds, create deployment build for each checkins to source version control systems.
  • With Continuous Delivery/Deployment (CD), the deployment build could be automatically deployed to a target environment, tested, and rolled-back for any failures.

Why CI/CD for B2C Service?

In non-CI/CD process, developer will have to manually ensure that there are no coding violations and unit tests coverage thresholds are met for coded customisation elements. Here, the deployment to Dev site and functional validations are done all by the developer manually. Later migrations from Dev to Pre-Prod/Test and further to Prod sites need to be done all manual as well.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!