Close popover

Table of Contents

Starting deployments

Version:

You can start deployments in a number of ways. For example, you can start a deployment manually if you are not using branches, by submitting a branch into the Merge Branches wizard, or by publishing application changes in App Studio to create a patch version of your application. Your user role determines if you can start a deployment.

  • Manually starting a deployment

    You can start a deployment manually if you are not using branches and are working directly in rulesets. You can also start a deployment manually if you do not want deployments to start automatically when branches are merged.

  • Understanding application changes made in App Studio

    You can publish application changes that you make in App Studio to the pipeline. Publishing your changes creates a patch version of the application and starts a deployment. For example, you can change a life cycle, data model, or user interface elements in a screen and submit those changes to systems in the pipeline.

  • Starting a deployment as you merge branches from the development environment

    In either a branch-based or distributed, branch-based environment, you can immediately start a deployment by submitting a branch into a pipeline in the Merge Branches wizard. The wizard displays the merge status of branches so that you do not need to open Deployment Manager to view it.

  • Understanding roles and users

    Define roles and users to manage which users can access Deployment Manager and which features they can access. For example, you can create a role that does not permit users to delete pipelines for a specific application.

Suggest Edit

Have a question? Get answers now.

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