The Pro project includes a single Git repository with a global
master branch and three main environments:
These environments are
read-only, accepting deployed code changes from branches pushed from your local workspace. See Pro architecture for a complete overview of the Pro environments. See Cloud Console for an overview of the Pro environments list in the project view.
The following graphic demonstrates the Pro develop and deploy workflow, which uses a simple, git-branching approach. You develop code using an active branch based on the
integration environment, pushing and pulling code changes to and from your remote, Active branch. You deploy verified code by merging the remote branch to the base branch, which activates an automated build and deploy process for that environment.
The integration environment provides a single, base
integration branch containing your Adobe Commerce on cloud infrastructure code. You can create one additional active environment branch. This allows for up to two active branches deployed to Platform as a service (PaaS) containers. There is no limit on the number of inactive environments.
Projects provisioned before June 5, 2020 had multiple, smaller Integration environments. If you need a larger Integration environment for testing and development, request an upgrade to Enhanced Integration environments. See the Integration Environment request article in the Adobe Commerce Help Center for details.
The project environments support a flexible, continuous integration process. Begin by cloning the
integration branch to your local project folder. Create a branch, or multiple branches, develop new features, configure changes, add extensions, and deploy updates:
Fetch changes from
Develop code on a local workstation, including Composer updates
Push code changes to remote and validate
integration and test
With a developed code branch and the corresponding configuration files, your code changes are ready to merge to the
integration branch for more comprehensive testing. The
integration environment is also best for:
Integrating third-party services—Not all services are available in the PaaS environment.
Generating configuration management files—Some configuration settings are Read Only in a deployed environment.
Configuring your store—You should fully configure all store settings using the integration environment. You can find the Store Admin URL on the integration environment view in the Cloud Console.
Every time you push code from your local workstation to the remote environment or merge code to an environment branch, the build and deploy scripts generate new code and provision the configured services to the remote environment.
Build script actions:
Site in the target environment continues to run during a build
Check and run Adobe Commerce on cloud infrastructure patches and hotfixes
Compile code with a build and deploy log
Check for Configuration Management, static content deployment occurs during this phase
Create or use a slug of unchanged code to speed up the process
Provision all backend services and applications
Deploy script actions:
Place the site in the target environment in a Maintenance mode
Deploy static content if not completed during Build
Install or update Adobe Commerce on cloud infrastructure
Configure routing for traffic
After the build and deploy process, your store comes back online with your latest code changes and configurations. See Deployment process.
Combine all verified code changes by merging your active development branch into the base
integration branch. You can test all your changes on the
integration branch before promoting changes to the Staging environment.
Staging is a pre-production environment that provides all services and settings as close to the production environment as possible. Always push your code changes from the
integration environment to the
staging environment so that you can perform thorough testing with all services. The first time you use the staging environment, you must configure services, such as Fastly CDN and New Relic. Configure payment gateways, shipping, notifications, and other vital services with sandbox or testing credentials.
It is best to thoroughly test every service, verify your performance testing tools, and perform UAT testing as an administrator and as a customer, until you feel that your store is ready for the production environment. See Deploy your store.
After thorough testing in the staging environment, merge to the production environment and thoroughly test using live credentials. The moment you launch your production site customers must be able to complete purchases and administrators must be able to manage the live store. See the following topics for a detailed, clear walk-through for deploying your store and going live:
Always push a copy of the production code to the Global
master in case there is an emergent need to debug the production environment without interrupting services.
Do not create a branch from Global
master. Use the
integration branch to create new, active branches for development and fixes.