Project Configuration Merge and Staging

This functionality becomes deprecated as of codeBeamer You must login to see this link. Register now, if you have no user account yet. and will not be enhanced in future releases. Please consider using the new Project configuration deployment functionality, which is designed to provide solution for deploying complex project configurations across codeBeamer instances.

The Project Configuration Merge and Staging solution allows users to move project configuration from one codeBeamer instance to another. Using this solution, you can set up your project, trackers, tracker fields, and workflows in a test environment first and ensure that everything works as expected before deploying the project configuration in the target codeBeamer instance.

The project configuration deployment process is controlled by a mapping wizard, which drives the user through the process step by step. Since the system does not know which configuration element in the source project to map on which element in the target system, you need to do the mapping manually. The system provides a default mapping (of trackers, tracker fields, and so on) in each step, however, the user needs to check all these mappings and make modifications if necessary. The default mapping is made based on the name and type of configuration elements.

During the deployment process, the user also has the possibility to delete or create elements from/in the target system if necessary.

For more information on how to prepare and deploy your project configuration, see section Prepare and Deploy Project Configuration.

When the mapping is defined, the deployment of the project configuration is initiated as a background procedure. During this procedure, the specified configuration of the source artifacts is applied to the target artifacts.

When the configuration deployment procedure is completed, the user receives an email notification. During the deployment procedure, a mapping file is also generated, which contains information about the mapping of artifacts defined by the user during the setup of the configuration deployment. This mapping file can be used to provide the default mapping in future deployment procedures: when the source instance configuration changes and you want to deploy the changes in the target system. As the mapping file contains the default mapping between the source and target elements, you do not need to define the mapping of all elements again, one by one, manually.

For more information on how to retrieve the mapping file, see section Download Project Mapping File.

For more information on how to automate the project configuration deployment procedure, see section Automate Project Configuration Deployment using Swagger API.