Generating and deploying release vehicles to test environments

This video explains how to generate a release vehicle and deploy it into a dedicated user acceptance testing (UAT) environment for testing.

The Generate Stage represents a critical phase in the life cycle of the release vehicle. During this stage, the system generates all the change request artifacts. Unlike a traditional change management system that generates Rules immediately after completion of a change request, Concurrent Change Management uses just-in-time Rule generation.

In this scenario, U+ Bank plans to generate its Quarter 1 release vehicle and deploy it to the existing UAT Alpha environment for testing.

As a Release Manager, log in to 1:1 Operations Manager and open the release vehicle that you want to generate. All the change requests included in the release vehicle must have a Resolved‑Completed status to generate the artifacts. Only finalized and approved changes are included in the generation process.

Now, you can generate the Rules. The generation process creates all artifacts in a new Branch that is designated for the release vehicle. This Branch uses the same name as the release vehicle ID, and the generated changes remain isolated within the release vehicle context until deployment. When the generation process completes successfully, you can submit and proceed to the next Stage.

After successful generation, the release vehicle status changes to Pending-Testing, which indicates that the release vehicle is generated but not yet deployed to the test environment.

If the system encounters any issues during generation, you receive a failure message and an option to regenerate. Use this option to retry the operation. In such cases, contact your technical team for assistance in identifying and resolving the underlying issue.

Testing refers to the validation that occurs in a higher dedicated test environment. In this optional Stage, you can run tests that are outside the scope of the Business Operations Environment. For example, integrating a Web Self-service Channel with Customer Decision Hub ensures that offers are presented with the appropriate treatments and that the selection of an offer initiates the correct fulfilment process in the Channel. 

Before deploying a release vehicle to the test environment, verify that the system generated it successfully and is in Pending‑Testing status. To begin the process, select the configured test environment, and then begin the deployment.

You can monitor deployment progress. When the deployment completes successfully, the status of the release vehicle changes to In‑Testing, which indicates that it has deployed to the UAT environment and is ready for testing.

To test multiple release vehicles simultaneously, you can create multiple business‑change test pipelines and applications in the testing cloud environment and test them in parallel.

You have reached the end of this video. You have learned:

• How to generate a release vehicle.
• How to deploy a release vehicle into a dedicated test environment.