Skip to main content


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

Configuring the development system for branch-based development

Updated on December 13, 2021

If you are using branches in either a distributed or nondistributed branch-based environment, configure the development system so that you can start deployments when branches are merged. Configuring the development system includes defining the URL of the orchestration server, creating development and target applications, and locking application rulesets.

  1. On the development system (in nondistributed environment) or the main development system (in a distributed environment), create a dynamic system setting to define the URL of the orchestration server, even if the orchestration server and the development system are the same system.
    1. Click CreateRecordsSysAdminDynamic System Settings.
    2. In the Owning Ruleset field, enter PegaDevOpsShared.
    3. In the Setting Purpose field, enter RMURL.
    4. Click Create and open.
    5. On the Settings tab, in the Value field, enter the URL of the orchestration server in the format http://hostname:port/prweb/PRRestService.
    6. Click Save.

      For more information about dynamic system settings, see Creating a dynamic system setting

  2. Complete the following steps on either the development system (in a non-distributed environment) or the remote development system (in a distributed environment).
    1. Use the New Application wizard to create a new development application that developers will log in to.
      This application allows development teams to maintain a list of development branches without modifying the definition of the target application.
    2. Add the target application of the pipeline as a built-on application layer of the development application by first logging into the application.
    3. In the header of Dev Studio, click the name of your application, and then click Definition.
    4. In the Built-on application section, click Add application.
    5. In the Name field, press the Down arrow key and select the name of the target application.
    6. In the Version field, press the Down arrow key and select the target application version.
    7. Click Save.
  3. Lock the application rulesets to prevent developers from making changes to rules after branches have been merged.
    1. In the header of Dev Studio, click the name of your application, and then click Definition.
    2. In the Application rulesets section, click the Open icon for each ruleset that you want to lock.
    3. Click Lock and Save.
  4. Copy the development repository that you configured on the remote development system to the source development system.
  5. If you are managing test cases separately from the target application, create a test application. For more information, see Managing test cases separately in Deployment Manager.
  6. Optional: To rebase your development application to obtain the most recently committed rulesets after you merge your branches, configure Pega Platform so that you can use rule rebasing.
    For more information, see Understanding rule rebasing.
  • Previous topic Creating repositories on the orchestration server and candidate systems
  • Next topic Configuring additional settings

Tags

Pega Platform 8.6 DevOps

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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