LinkedIn
Copied!

Table of Contents

Applying DevOps concepts in the Pega Platform

Version:

Only available versions of this content are shown in the dropdown

Use DevOps practices such as continuous integration and continuous delivery to quickly move application changes from development through testing to deployment on your production system. Use Pega Platform tools and common third-party tools to implement DevOps.

The release pipeline in the following diagram illustrates the best practices for using Pega Platform for DevOps. At each stage in the pipeline, a continuous loop presents the development team with feedback on testing results. This example includes the following assumptions:

  • Pega Platform manages all schema changes.
  • Jenkins is the automation server that helps to coordinate the release pipeline, and JFrog Artifactory is the application repository; however, other equivalent tools could be used for both.

Open DevOps release pipeline overview

  • Developing Pega applications

    Pega Platform developers use Agile practices to create applications and commit the changes into branches in a shared development environment. Automated and manual testing provides rapid feedback to developers so that they can improve the application.

  • Understanding the DevOps release pipeline

    Use DevOps practices such as continuous integration and continuous delivery to quickly move application changes from development through testing to deployment on your production system. Use Pega Platform tools and common third-party tools to implement DevOps.

  • Development workflow

    In a DevOps workflow, the most important best practice for application developers to adopt is continuous integration. Continuous integration is the process by which development changes to an application are integrated as frequently as possible, at least once a day and preferably multiple times a day, every time developers complete a meaningful unit of work.

  • Understanding best practices for version control in the DevOps pipeline

    As a best practice, use semantic versioning when changing the version number, because it offers a logical set of rules about when to increase each version number.

  • Migrating application changes

    With minimal disruption, you can safely migrate your application changes throughout the application development life cycle, from development to deployment on your staging and production environments. In the event of any issues, you can roll back the deployment and restore your system to a state that was previously known to be working.

  • Deploying application changes to your staging or production environment

    As part of the Standard Release process, after you set up and package a release on your shared development environment, you can deploy your application changes to your staging or production environment.

  • Packaging a release on your development environment

    As part of the Standard Release process for migrating your application changes from development to production, you set up and package the release on your shared development environment.

  • Understanding application release changes, types, and processes

    The following tables provide information about the types of changes that you can make within a release, the release types, and the release management process to follow based on the types of changes that you want to deploy.

Have a question? Get answers now.

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