Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Understanding best practices for using branches with Deployment Manager

Updated on April 5, 2022

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.

  • Previous topic Understanding pipelines in an environment without branches
  • Next topic Using branches with Deployment Manager

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us