Skip to main content

Understanding best practices for using branches with Deployment Manager

Suggest edit Updated on April 13, 2020

Follow these best practices when you use branches in your Deployment Manager pipelines. The specific practices depend on whether you have a single development team or multiple development teams in a distributed environment.

If you use branches for application development in a non-distributed environment, developers work on branches and merge them on the development system, after which the continuous delivery pipeline is started automatically or manually.

In a distributed branch-based environment, you can have multiple development systems, and developers author and test the application on a remote development system. They then merge their changes on a source development system, from which the changes are merged and moved in the Deployment Manager workflow.

For more information about best practices to follow in the DevOps pipeline, see Understanding the DevOps release pipeline.

  • Using branches with Deployment Manager

    Best practices for using branches in Deployment Manager depend on whether you have a single development team or multiple teams in a distributed environment.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us