Global variables control actions across each phase of the Commerce deployment process: build, deploy, and post-deploy. Because global variables impact every phase, you must set them in the
global stage of the
stage: global: GLOBAL_VARIABLE_NAME: value
For more information about customizing the build and deploy process:
Overrides the minimum logging level for all output streams without changing the code. This helps when troubleshooting problems with deployment. For example, if your deployment fails, you can use this variable to increase the logging granularity globally. See Log levels. The
min_level value in Logging handlers overwrites this setting.
stage: global: MIN_LOGGING_LEVEL: debug
The setting for the
MIN_LOGGING_LEVEL variable does not change the log level configuration for the file handler, which is set to
debug by default.
Enable generation of static content when requested by a user (SCD). This is ideal for the development and testing workflow, because it decreases the deployment time.
Pre-loading the cache using the
post_deploy hook reduces site downtime. The cache warming is available only for Pro projects that contain Staging and Production environments in the Project Web Interface and for Starter projects. Add the
SCD_ON_DEMAND environment variable to the
global stage in the
stage: global: SCD_ON_DEMAND: true
SCD_ON_DEMAND variable skips the SCD in both phases (build and deploy), clears the
var/view_preprocessed folders, and writes the following to the
return array( ... 'static_content_on_demand_in_production' => 1, ... );
Allows you to increase the maximum expected execution time for static content deployment.
By default, Adobe Commerce sets the maximum expected execution to 900 seconds, but in some scenarios you might need more time to complete the static content deployment for a Cloud project.
stage: global: SCD_MAX_EXECUTION_TIME: 3600
If you have issues with static content files in your application after deployment, such as missing custom theme files, increase the maximum expected execution time to 900 seconds or higher.
true to prevent generating static content for parent themes during the build and deployment phases. When this option is set to
true, less static content is generated, which improves your overall build and deployment times.
stage: global: SCD_NO_PARENT: true
true to run Baler after performing static content deployment.
stage: build: SCD_USE_BALER: true
You must install and configure the Baler module before using this feature. Because Baler is in alpha release, enable this option only on Staging environments.
ece-tools2002.0.13 and later
false—for earlier versions of
Enables or disables copying static view files to the
<magento_root>/init/ directory at the end of the build stage. If set to
true files are not copied and HTML minification is available on request. Set this value to
true to reduce downtime when deploying to Staging and Production environments.
view_preprocesseddirectory to the
<magento_root>/init/directory at the end of the build phase, and restores the directory in the
<magento_root>/vardirectory at the beginning of the deploy phase.
true—Enables on-demand HTML minification; does not copy the
<magento_root>/init/directory at the end of the build phase.
SKIP_HTML_MINIFICATION environment variable to the
global stage in the
stage: global: SKIP_HTML_MINIFICATION: true
X_FRAME_CONFIGURATION variable to change the
X-Frame-Options header configuration for your Adobe Commerce site. This configuration controls how the browser renders a page in a
<object>. Use one of the following options:
DENY—Page cannot be displayed in a frame.
SAMEORIGIN—(The default Adobe Commerce setting.) Page can be displayed only in a frame on the same origin as the page itself.
ALLOW-FROM <uri> option has been deprecated because Adobe Commerce-supported browsers no longer support it. See Browser compatibility.
X_FRAME_CONFIGURATION environment variable to the
global stage in the
stage: global: X_FRAME_CONFIGURATION: SAMEORIGIN