Devops - Version management

Pega-as-a-Service
,
1

I have a version management question. I have 2 teams working on enhancements on the same rule set. The enhancements are being tested in the test environment in an incremental fashion. Now one enhancement is ready for production release. How do I make sure that the configuration for the other enhancement is not migrated to PROD?

2

@PadmaK42

To ensure that only the approved enhancement is migrated to production, you can use version control and branching strategies. Here’s a suggested approach:

  1. Create a new branch in your version control system for the enhancement that is ready for production release. This branch will contain only the changes related to that enhancement.

  2. Merge the changes from the development branch into the new branch. This will ensure that the enhancement is complete and tested before it is deployed to production.

  3. Deploy the new branch to the production environment.

  4. Keep the other enhancement in the development branch until it is ready for production release.

By using this approach, you can ensure that only the approved changes are migrated to production while keeping the other enhancement separate from the production environment until it is ready. You can also use a similar approach to manage multiple enhancements being developed by different teams simultaneously. Each team can work on a separate branch, and changes can be merged into the main branch only after they have been reviewed and approved.

3

@PadmaK42 you could design to use two different pipelines for different releases.

If you are using a same pipeline, you could leverage ‘multispeed’ capability in DM, which has some constraint like the enhancement that is ready for Production needs to be in an earlier deployment package.

If you have the two enhancements in a same deployment package, then it can be a bit tricky. In our project, we manually remove the enhancement that is not ready for Production release and only release the other enhancement that is ready for Production.

In the past, we have asked Pega DM product team for enhancement to rollback the code at a branch level, but i haven’t seen this yet.