[NOTICE] End of life announcement for Commerce Legacy Build Service

As of September 30, 2026, Optimizely stops updating and enhancing the Configured Commerce legacy build service, which runs on TeamCity. Build service v2, which runs on Kubernetes, replaces the legacy TeamCity-based service and adds scalability and security. Optimizely recommends that Configured Commerce Cloud customers migrate to build service v2 before September 30, 2026.

Migrate to build service v2

This process requires no code changes and causes no downtime or disruption. Configured Commerce customers still using the legacy build service must complete the following two steps:

1. Install the build service v2 GitHub app in all Configured Commerce extension repositories. This short configuration change lets build service v2 access the repository and build the connected cloud instances. See Build service v2 for Optimizely Configured Commerce for details.

   you can also remove the old insite-team-city user from the repositories because build service v2 does not require it.

2. Submit one support ticket requesting a build service v2 upgrade for all your CFG instances. All customer instances must be migrated to the new service via the same ticket. Include the following repository details for each instance in the support ticket:
   • Git Uniform Resource Identifier (URI) – The URI of the repository used for the Commerce instance, in the format git@github.com:organization/repository.git

   • Branch name – The branch name used for the Commerce instance. 

     Branch rules differ in build service v2. See Configure existing instances.

   • Build alerts contact email – The email address that receives build success or failure notifications for the Commerce instance, typically a group address.

Benefits of build service v2

Build service v2 runs on Kubernetes instead of the legacy TeamCity-based system. It provides scalability and security improvements over the legacy service:

• Uses the internal Kubernetes infrastructure for Configured Commerce to scale build resources dynamically, which reduces queue and build time.
• Uses a GitHub App to receive webhooks that notify build service v2 of code changes, which streamlines setup and shortens build queue times.

Other key benefits:

• Configure builds yourself through Mission Control.
• Maintained allowlist of third-party packages for Configured Commerce.
• Improved logging and error visibility for build service configurations.
• .NET Core build and deploy support.