Deployment process

See the Cloud release scheduleCloud release schedule for important dates, release type, and cadence information.

Upgrade your Configured Commerce instance before requesting deployment.

If Optimizely identifies an issue that requires immediate resolution outside the normal release cadence, Optimizely builds a hotfix.

Optimizely only builds hotfixes for the current cloud release. Applying the hotfix will automatically update your environment to the current cloud release, if applicable. See the release notesrelease notes for a list of hotfixes for the current release. You should follow these articles to receive updates.

Applying a hotfix increases your current month's build number, so expect that the final numbers in the version will not match.

Optimizely tests hotfixes specifically for the identified issue and does not perform full regression testing. You or the partner must test all hotfixes in the Sandbox environment before requesting deployment to Production.

The Optimizely Service Desk handles new deployment requests for customers in containers. The deployment process varies based on your Configured Commerce instance's hosting infrastructure version. See Infrastructure overview to learn more.

Optimizely Configured Commerce uses a rolling deploy strategy for its environments. This means that there are always containers available to the load balancer. Even during a deploy, websites should not appear as being unavailable to customers.

Optimizely Configured Commerce uses a rolling deploy strategy for its environments. This means that there are containers available to the load balancer at all times. Even during a deployment, websites should be available to customers. Site redeployment is scheduled with the Optimizely Support Service Desk team for the changes to take place. Use the ticket form for redeployment requests.

Non-production environment deployment is automatically performed when you commit to the attached git branch. You receive an email upon success or failure.

Configured Commerce does not automatically deploy production environments. You can self-service production deployments through Mission ControlMission Control. See Base Code DeployBase Code Deploy and Extension DeploymentExtension Deployment for information.

Scheduling

Deployments can be scheduled with Service Desk in 30 minute intervals based on the scheduling windows listed in the following section. All request approvals depend on available resources and your request is either approved or you are presented with other time options if the original time requested is not available. Optimizely recommends 24 hours notice for deployment, but requested times are not guaranteed until the Service Desk has confirmed your time slot.

Extensions-only deployments are available through the Service Desk request during the hours set in your Service Level Agreement.

Scheduling

Scheduling

Cancellation

Respond to your original deployment request Support ticket to cancel the scheduled deployment.

You can roll back the Configured Commerce base code and extensions code as an emergency recovery if an upgrade breaks your environment.

Currently, Optimizely does not support rolling back extensions after a deployment. To deploy a previous extension version follow these steps:

Example: