Learn how to configuring non-production pipelines to test the quality of your code before deploying to production environments.
In addition to production pipelines which deploys to stagings and production environments, you can also set up non-production pipelines to validate your code.
There are two types of non-production pipelines:
You can edit pipeline settings after the initial setup.
Once you have set up your program and have at least one environment using the Cloud Manager UI, you are ready to add a non-production pipeline by following these steps.
Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization and program.
Access the Pipelines card from the Cloud Manager home screen. Click on +Add and select Add Non-Production Pipeline.
On the Configuration tab of the Add Non-Production Pipeline dialog, select the type of non-production pipeline you with to add.
Provide a Non-Production Pipeline Name to identify your pipeline along with the following additional information.
Deployment Trigger - You have the following options when defining the deployment triggers to start the pipeline.
If you choose to create a Deployment Pipeline you will also need to define the Important Metric Failures Behavior.
Click Continue.
On the Source Code tab of the Add Non-Production Pipeline dialog, you must select which type of code the pipeline should process.
The steps to complete the creation of your non-production pipeline vary depending on the option for Source Code you selected. Follow the links above to jump to the next section of this document to complete the configuration of your pipeline.
A front-end code pipeline deploys front-end code builds containing one or more client-side UI applications. See the document CI/CD Pipelines for more information about this type of pipeline.
To finish the configuration of the front-end code non-production pipeline, follow these steps.
On the Source Code tab, you must define the following options.
See the document Adding and Managing Repositories to learn how to add and manage repositories in Cloud Manager.
Click Save.
The pipeline is saved and you can now manage your pipelines on the Pipelines card on the Program Overview page.
A full-stack code pipeline simultaneously deploys back-end and front-end code builds containing one or more AEM server applications along with HTTPD/Dispatcher configuration. See the document CI/CD Pipelines for more information about this type of pipeline.
If a full-stack code pipeline already exists for the selected environment, this selection will be disabled.
To finish the configuration of the full-stack code non-production pipeline, follow these steps.
On the Source Code tab, you must define the following options.
See the document Adding and Managing Repositories to learn how to add and manage repositories in Cloud Manager.
Git Branch - This option defines from which branch in the selected the pipeline should retrieve the code.
Ignore Web Tier Configuration - When checked, the pipeline will not deploy your web tier configuration.
Pipeline - If your pipeline is a deployment pipeline, you can choose to run a testing phase. Check the options you wish to enable in this phase. If none of the options are selected, the testing phase will not be displayed during pipeline execution.
Click Save.
The pipeline is saved and you can now manage your pipelines on the Pipelines card on the Program Overview page.
A web tier config pipeline Deploys HTTPD/Dispatcher configurations. See the document CI/CD Pipelines for more information about this type of pipeline.
If a web-tier code pipeline already exists for the selected environment, this selection will be disabled.
To finish the configuration of the web-tier code non-production pipeline, follow these steps.
On the Source Code tab, you must define the following options.
See the document Adding and Managing Repositories to learn how to add and manage repositories in Cloud Manager.
conf.d
, conf.dispatcher.d
, and opt-in
directories./dispatcher/src
.Click Save.
If you have an existing full-stack pipeline deploying to an environment, creating a web tier config pipeline for the same environment will case the existing web tier configuration in the full-stack pipeline to be ignored.
The pipeline is saved and you can now manage your pipelines on the Pipelines card on the Program Overview page.
With front-end pipelines, more independence is given to front-end developers and the development process can be accelerated.
Please refer to the document Developing Sites with the Front-End Pipeline for how this process works along with some considerations to be aware of in order to get the full potential out of this process.
If you want dispatcher packages built as part of your pipeline, but do not want them published to build storage, you can disable publishing them, which may reduce pipeline run duration.
The following configuration to disable publishing dispatcher packages must be added via your project pom.xml
file. It is based on an environment variable, which serves as a flag you can set in the Cloud Manager build container to define when dispatcher packages should be ignored.
<profile>
<id>only-include-dispatcher-when-it-isnt-ignored</id>
<activation>
<property>
<name>env.IGNORE_DISPATCHER_PACKAGES</name>
<value>!true</value>
</property>
</activation>
<modules>
<module>dispatcher</module>
</modules>
</profile>