Operations That Do Not Update Source Traces
Some configuration management operations do not automatically update source traces. In order for the source trace to reflect the change, you need to modify how you perform these operations. This involves updating the source trace as part of the operation, or using a check source trace command to identify invalid source traces and fixing them manually.
• Subproject operations
Subproject operations change the project context of the members in the subproject but do not update the source traces to those members.
• Operations that are not recorded in a change package.
The following operations change the project context of a member but are not recorded in change packages, so source traces are not updated:
◦ Drop development path
◦ Delete project
◦ Restore project
◦ Purge project
◦ Delete revision
• Operations on shared members in multiple projects
If the traced member belongs to a project that is shared in multiple editable project configurations (not build projects), any member operations resulting in a new member revision automatically update the source traces in the project listed in the change package, but traces to the same member in other shared projects are not updated.
|
|
Sharing subprojects in multiple editable project configurations is not recommended in a functional safety environment.
|
