Article - CS125580
How to merge two different revision branches to mainline in Integrity Lifecycle Manager using Merge Child Development Path
Modified: 09-Feb-2017
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 2009 to 10.9
Description
- How to merge a variant path with two or more different revision branches to the mainline?
- Attempting to use mergechilddevpath command fails with errors
- Member <member name>: *** no action will be performed due to errors ***
- Error: Two revisions (<revision version 1> from change package <cpid 1> and <revision version 2> from change package <cpid 2>) in the change packages are in conflict. They refer to two different revision branches <revision version 1> and <revision version 2>. All modifications must apply to the same revision branch. If you wish to accept the most recent revision (<revision version 2>) for this member, rerun the command with the Ignore Cross-Branch Entries (--ignoreBranches) flag.
- Reference Change Packages: <cpid 1>, <cpid 2>
This is a printer-friendly version of Article 125580 and may be out of date. For the latest version click CS125580