Nick D
-
Posts
4 -
Joined
-
Last visited
Posts posted by Nick D
-
-
Hello, I'm looking to see if anyone can provide insight into exactly what the "--noninteractiveresolution" option for cm merge does under the hood. My company has used it as part of an automated merge tool after coming across it in this thread, but recently we've been encountering an issue where child branches are getting spun off of destination branches with the same name (i.e: /main/dev/destination/destination-2 is branching off of /main/dev/destination). Given the timing of when the branches are created and when the command is called, I was wondering if there is a link between the two and I'd like to start by getting more information on what "--noninteractiveresolution" does outside of preventing Plastic for asking the user to perform manual conflict resolution.
-
Thank you so much. While that didn't give me exactly what I was looking for (that returned changeset ID whereas I needed changeset number), I was able to modify it a bit and get the result I was looking for with this in Powershell:
$Changesets = cm find changesets --nototal $LatestChangeset = ($Changesets[-1] -Split "\s+")[1] -
Hello, I was wondering if anyone on here could help me with something that seems like it should be fairly simple.
I'm trying to figure out a way to determine the latest changeset number in a given repository via Plastic CLI. I found this thread in regards to what appears to be the same issue:
But unfortunately the answer to this thread doesn't actually address what I need.
What exactly is the "--noninteractiveresolution" option doing in cm merge
in Branching and merging
Posted
Yes, Xlinks are being utilized in our Repository structure. The issue in question is occurring when changes are getting merged into wXlinks.