Best Practices for the Project Configuration Deployment
Ensure that the Source and Target Codebeamer Versions Match
Deployment between different Codebeamer versions is not recommended because it can result in a deployment failure or data loss.
Exercise Caution When Changing Imported Entities on the Target Instance
Check if an imported entity was deleted on target system and if it can be imported again. In these cases, the UUID already exists in the target system, but the entity is deleted and might not be found by manager Java classes such as TrackerManager. The general approach to resolve this is to recover the entity during import. Additional information regarding this topic is available in Project Configuration Deployment - Technical Details.
Carefully Manage Permissions for Users Initiating the Deployment
The deployment process updates and extends permissions for the project members, groups, project roles and tracker permissions. To prevent a data loss, verify any updates to these entities.
Regularly Check and Update Configurations Post-deployment
To avoid a slow deployment process and reduce the number of potential deployment issues to handle, PTC recommends performing deployments at regular time intervals.
Be Aware of the Limitations When Exporting Specific Entities
Before every deployment, consider the list of known limitations at Known Limitations for the Project Configuration Deployment.
Use Selective Deployment for Incremental Updates
When performing a deployment, aim to be as specific as possible by using and selecting deployment options as needed.
Verify and Validate Deployment Results Using Baselines
On the target instance, consider creating one baseline before and another one after the deployment process. After the deployment is completed, you can have a report of all the deployment changes by using the Comparing Baselines feature.
Check Invalid Query Formats
Invalid query formats can break the import process. Before deployment, perform an extensive analysis on the user-provided queries to resolve corrupt formats. Refer to Reports for additional details.
Verify How Inheritance is Handled
• Tracker inheritance is removed during a normal deployment import process. To verify this step, ensure to cover the following points:
1. Check if the feature still works when the tracker inheritance is removed during import.
2. Check if the entity can be inherited and if it is copied over to the child tracker or child project during the import.
• If the tracker inheritance is retained by using the Import tracker inheritance option, do the following:
1. Check all the tracker configuration updates on the deployed template and derived trackers.
2. Ensure to enable the Import tracker inheritance option.
Verify How Tracker Views Are Handled
Every import recreates all the tracker views. Check the following for the import process:
1. Correct resolution of the inherited view reference.
2. Correct copy of the inherited view to the child tracker.
Verify the Password and Encryption Features
Consider securing the import process on the target instance by including a password to perform the project deployment.
Verify Computed Fields
Codebeamer recalculates the computed fields in every tracker after the deployment import. Ensure that the computed fields references are resolved correctly.
 |
You can avoid the field recalculation by selecting Skip refresh computed fields on tracker items when applying the project deployment on the target environment.
|