Life cycle of a release vehicle
A release vehicle is a Case Type in Pega 1:1 Operations Manager that groups related change requests for coordinated testing and deployment.
Video
Transcript
Welcome to this overview of the life cycle of a release vehicle in Pega 1:1 Operations Manager.
A Release Vehicle is a managed unit of work that groups related change requests so they can be tested and deployed together. It helps teams work in parallel without conflicts or time‑consuming manual merges.
Traditional revision management works like a single train on a fixed track. Every change request must get on the same train, and a delay in one can hold up the entire journey. This creates bottlenecks and slows delivery.
Concurrent Change Management, or CCM, takes a different approach. Instead of one train, it introduces release vehicles that operate like a fleet of buses. Each bus carries its own set of changes and moves independently. This independence reduces merge conflicts, provides flexibility, and prevents one team’s delays from impacting others.
Each release vehicle progresses through five stages: Create, Plan, Generate, Test, and Deploy. These stages ensure that changes are captured, artifacts are generated, tested, and safely promoted to production.
In the stage, the Release Manager defines the basic information for a release vehicle. A release vehicle can be deployable or non-deployable. Non-deployable release vehicles are limited to testing and cannot be promoted to production.
During the stage, change requests are organized. Teams can add, remove, or reorder requests within a release vehicle. CCM allows teams to move change requests between release vehicles easily. Dependencies are automatically detected and highlighted.
The stage creates artifacts for the changes in a release vehicle. All change requests must be in Resolved-Completed status before generation. The system uses Just-in-Time rule generation to create rules in a temporary branch dedicated to the release vehicle. The release vehicle can be tested using the Customer profile viewer and Simulations in Business Operations Environment before generation.
In the stage, changes are validated in a dedicated test environment. This stage supports advanced channel and integration testing. The Test Manager oversees testing and provides approval. If the test environment is enabled, all release vehicles must go through this stage. This setting cannot be changed for individual release vehicles.
Finally, in the stage, approved release vehicles are promoted across environments. After successful deployment, the release vehicle is marked Resolved-Deployed. Multiple release vehicles can be active at the same time, but only one can be deployed at a time.
Release vehicles transform change management from a single train journey into a flexible fleet of buses. This enables organizations to adapt quickly to market needs, support complex business requirements, and deliver continuous improvements.
You have reached the end of this video. What have you learnt?
- A release vehicle groups related change requests for coordinated testing and deployment.
- It progresses through five stages—Create, Plan, Generate, Test, and Deploy—enabling parallel work, reducing merge conflicts, and accelerating delivery.
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
¿Quiere ayudarnos a mejorar este contenido?