Table of Contents

Article

Development workflow in the DevOps pipeline

Follow these best practices to develop or improve your application with DevOps in a shared development environment. The specific practices depend on whether you have a single development team or multiple development teams.

Single development team

Single teams typically work on a single development server and collaborate on the production application. To practice continuous integration, use a team application layer, branches, and release toggles.

  • Build a team application layer that is built on top of the main production application. The team application layer contains branches, tests, and other development rulesets that are not intended to go into production. For more information, see Using multiple built-on applications.
  • Create a branch of your production ruleset in the team application. For more information, see Adding branches to your application.
  • Perform all development work in the branch.
  • Optional: Use release toggles to disable features that are not ready for general use. Using toggles allows you to merge branch content frequently even if some content is not final. For more information, see Release toggles.
  • Create formal review tasks for other members of the development team to review your content. For more information, see Creating a branch review.
  • Use the branch developer tools to review the content and quality of your branch. For more information, see Reviewing branches.
  • Lock the branch. For more information, see Locking a branch.
  • Frequently merge the branch from the team application layer to the production rulesets. For more information, see Merging branches.
  • Start the continuous delivery pipeline for your application. For more information, see DevOps release pipeline overview.

Multiple development teams

If you have multiple teams working on the same application, each team should have a separate development server. A central Pega® server acts as a system of record (SOR). The central SOR allows teams to integrate features into the application in a controlled manner and avoid unexpected conflicts between teams working in the same rulesets. To practice continuous integration, use a team application layer, branches, and release toggles, and use the Pega repository as the SOR.

  • Build a team application layer that is built on top of the main production application. The team application layer contains branches, tests, and other development rulesets that are not intended to go into production. For more information, see Using multiple built-on applications.
  • Create a branch of your production ruleset in the team application. For more information, see Adding branches to your application.
  • Perform all development work in the branch.
  • Optional: Use release toggles to disable features that are not ready for general use. Using toggles allows you to merge branch content frequently even if some content is not final. For more information, see Release toggles.
  • Create formal review tasks for other members of the development team to review your content. For more information, see Creating a branch review.
  • Use the branch developer tools to review the content and quality of your branch. For more information, see Reviewing branches.
  • Lock the branch. For more information, see Locking a branch.
  • Push the branch to the Pega repository SOR. For more information about pushing branches to repositories, including the Pega SOR, see Pushing a branch to a repository.
  • Merge the branch into the Pega SOR. For more information, see Merging branches.
  • Rebase the rules on your development system to get the latest versions of rules from the Pega SOR. For more information, see Rebasing rules.
  • Start the continuous delivery pipeline for your application. For more information, see DevOps release pipeline overview.

Published April 26, 2017 — Updated October 16, 2017


88% found this useful

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.