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 pipelines in an environment without branches

Updated on April 5, 2022

If you do not use branches for application development, but you use ruleset-based development instead, you configure the continuous delivery pipeline in Deployment Manager.

The workflow of tasks in this pipeline is as follows:

  1. Developers update rules and check them in directly to the application rulesets on the development system.
  2. The product rule that contains the application rules to be packaged and moved through the systems in the pipeline is on the development system.
  3. Continuous delivery is started manually at a defined schedule by using Deployment Manager.

The following figure describes the workflow of a pipeline in an environment without branches.

Workflow in an environment without branches
Workflow in an environment without branches

  • Previous topic Understanding pipelines in a branch-based environment
  • Next topic Understanding best practices for 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