Integrating branches with Merge pipeline
Integrating application changes rapidly by making sure that the changes do not create an impact is essential in building high-quality applications. Deployment Manager simplifies this process by using merge pipelines to validate, merge, and promote branch changes into the main application while maintaining strong quality, security, and governance controls
Merge pipeline overview and setup
The merge pipeline contains default quality and compatibility checks before integrating Rule changes into the application.
The out-of-box Merge pipeline template helps ensure that the merge starts only after validating branch changes against quality gates, such as guardrails, branch reviews, and automated tests, and compatibility gates that are configured on the merge pipeline. If the merge criteria are met, the branch changes are merged. If any of the gates fail, the pipeline rejects the merge request and notifies you of the failure.
Setting up a merge pipeline is the first step in establishing a structured integration process. By using merge pipelines, developers can submit branches for merging after reviewing their quality on the Branch Quality dashboard.
For more information, refer to Creating a merge pipeline.
Merge initiation
Developers can initiate a gated merge directly within Dev Studio from the branch they are working on.
In a branch-based environment, you can start the deployment immediately by submitting a branch into a merge using from Dev-Studio through the Merge Branch wizard which also shows the real-time merge status of branch eliminating the need to open Deployment Manager separately.
Check your knowledge with the following interaction:
In the following image shows a Merge pipeline. Click the + icons to view the different Branch tasks available on the pipeline:
Streamline Continuous Delivery (CD)
To streamline application deployments, Deployment Manager supports Continuous Delivery (CD). You can automatically deploy the main application to higher environments after each successful merge.
Use a dedicated Trigger deployment Task in the Merge pipeline to continue with the CD process which deploys the main application with every successful merge to higher environments for extensive quality and security checks. This helps assess if the change is production-ready.
For more information, see Triggering a deployment.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?