I have two repositories dev and Plastic, I want to link folders from dev into Plastic.
I have gotten this to work using the CLI, however at some point it just started failing such that when I create the partial readonly Xlink from the command line it would show the link being made to the right folder at the right repo at the right changeset but it would not download the files on the Plastic workspace.
Even copy/pasting the old commands I saved in my batch file did no longer work. The only rerequisite I could find in the documentation was to make sure the directory did not exist before creating it.
-
Make sure there is no Assets\Editor in Plastic
-
cm xlink Assets\Editor /Assets/Editor cs:2@dev
-
Console echos Xlink is set up as expected to the cloud repo
-
Find correct Xlink in the UI
-
Check in Xlink folder from the pending changes tab
-
Update the workspace
-
Assets/Editor remains empty
-
Changeset 2 on dev in the cloud has all the files
Am I missing something? Is there a hard limit to the number of Xlinks you can create between repos? Is something external failing somewhere?
Hi, I’m afraid we cannot easily reproduce the problem. Can you open a ticket at devops-vcs-support@unity3d.com?
We may need to arrange a meeting for further debugging.
We are in a similar state with partial xlinks, on one machine in our network they just won’t sync. We created partial readonly xlinks as follows
cm xlink test /path/to/target-folder 1323@target-repository@server:8087
This command completed successfully and the change was then checked-in. The xlink is in use on multiple clients in our network (all Windows systems), but there is one machine (macOS) that is just unable to update the workspace with a partial xlink inside of it. A workspace update yields an error for the xlink “The changeset xyz content cannot be loaded.” In the workspace explorer, the folder is marked as “unresolved xlink”. Removing and recreating the xlink on the affected machine does lead to the same error. We simply can not use repositories that use partial xlink on this machine.
Plastic version is 11.0.16.9009. We had so many frustrating hours working around xlinks that we probably resort to dumping all of them in our repos and just write some bash scripts that copy folders around.
Attached are some screenshots on the issue.
We use Plastic for so many years and most of the time, source control just works. But once in a while we have some issues with it that quickly stall our whole development. Plastic is notoriously bad at messaging the user what’s wrong. Seriously, “The changeset xyz content cannot be loaded.” is a bullshit message, what should I do with this? At least point me into a direction allowing me to understand what’s wrong. The online documentation of Plastic always assumes everything to be working fine and has almost no debugging hints when things go bad. Btw, its SEO is atrociously bad, making it unbelievably hard to find information to problems I encountered and the website’s search is a joke. I find myself digging through old forum posts, hoping to find people with similar problems I have.
Also, after many years of use, I am still not able to fully understand Plastics inner workings. I don’t know what config file configures what and why it’s needed. I don’t get how all the tools interact with each other. I’m not even able to find relevant logs and don’t know how I possibly can get Plastic to output more information to me. It still does not feel like I can control the tool I use. This is very bad.
Hi, Can you open a ticket at devops-vcs-support@unity3d.com?
Its gonna be easier and faster to debug the issue there and maybe have a meeting in your time.
