Search the Community

We have 2 Plastic Enterprise servers in Bangalore and London. Both servers act as Master. Currently using triggers to replicate the Repositories between 2 servers. Issue here is the replication starts only on trigger. Is there any better way to auto sync all the repositories between 2 servers at server level instead of repository level? Will deploying Cloud extension on these servers help to achieve auto syncing of all Repos on daily basis? Thanks

I am attempting to sync an on-prem PlasticSCM server with a Plastic Cloud account using the sync view functionality. One of the repos gives me the following error message when I attempt the sync: An error occurred during the replication: The source branch has two heads. Merge from cs:xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx to br:/main to unify the heads. I know from some research (here in these forums and Stack Overflow) that this is an issue where there are two HEADs in the repo, and that I need to merge one into the other in order for this to get fixed, but I am unsure how to identify the offending changeset. Playing around with the Linux app, I believe that the `cs:xxxxxxx-...` is the GUID of the changeset I care about, but I am unsure if this is the case. Am I correct in that assumption? A second question, which is not terribly important (mostly curious), is what `cm` command(s) would be able to help me identify the second HEAD?