Build and deploy notifications

  • Updated

Mission Control serves as Configured Commerce's build and deployment alerting system. It supports several notification and email types to keep teams informed at every step of the process.

Most of this functionality is available for only Configured Commerce instances using the v2 build service. If your instance is on the legacy build service, you should follow the no-code process to upgrade.

Email alerts

Mission Control sends build and deployment emails to the BuildAlertContactEmail defined within the Instance Details > Properties tab.

Mission Control sends the following types of email alerts:

  • Build and deploy success – Sent when both steps complete successfully.
  • Build succeed and deploy failed – Sent when the build completes, but deployment fails.
  • Build failure (deploy not triggered) – Sent when the build fails and deploy never starts. This is the only email that includes build logs.
  • Build success (production only) – Sent when the production build completes successfully. Production builds are not deployed automatically and must be deployed through mission control.

Dashboard notifications

The following notifications display on the Mission Control Dashboard and the Configured Commerce Instance Details > Notifications tab.

  • Build started (commit detected)
    • Example – A new commit for cfginstance1 (sandbox-az) has been detected, and the build process has started. Commit: 7c485…
  • Build completed (deploy in progress)
    • Example – A build [5.2.2501.1535-sts -- 20260303T150611Z-9a22b24] for your sandbox-az instance has been completed successfully.
  • Build and deploy succeeded
    • Example – Deployment for cfginstance1 (sandbox-az) has succeeded. Build 20260302T130639Z-0f754a8-5.2.2602.377-rc was deployed successfully
  • Build succeeded and deploy failed
    • Example – Deployment for cfginstance1 (sandbox-az) has failed. Build 20260302T143608Z-1d7c834-5.2.2501.1535-sts completed successfully, but the deployment step encountered an error.
  • Build failed (deploy not triggered)
    • Example – Build failed for your instance! Please check your designated build alert email for information and review the log file for details.
  • Deployment failed due to extension script issues

    • Example – Alert Opened: CFG - Log Monitor - Extension Script Failure on kube_namespace:isc-sandbox-az-test,service:test-commerce: @workflow-mc-alert Sql Error: Violation of PRIMARY KEY constraint 'PK_JobDefinitionParameter'. Cannot insert duplicate key in object 'dbo.JobDefinitionParameter'. The duplicate key value is (0000-0000-0000-0000-0000). Script: Extensions.DatabaseScripts.JobDefinitions.2025.03.18.01.test.sql

      When the script failure is resolved, an "Alert Resolved" is logged for the same issue.

Mission Control skips the deployment step if the "backend" property does not match any of the extensions.dll files in the repository.

Example – Instance cfginstance1 will not be deployed because the correct Extensions.dll file was not found for the Linux environment. See Update the Extensions code to use .NET 8.0+ and build.