Search Unity

Question A way to forcibly download new changesets and replace local changes?

Discussion in 'Unity Version Control' started by MOLB, Nov 26, 2022.

  1. MOLB

    MOLB

    Joined:
    Dec 19, 2012
    Posts:
    41
    Our team works on projects in larger scales. Due to some connection issues and instabilities with Plastic, there are sometimes disconnects while downloading larger changesets. When reopening Plastic, the files that have already been downloaded create directory conflicts, and these have to be resolved manually. Even when choosing "Apply this action for the next ... conflicts", it can take several hours, even days to complete when there are thousands of files involved. This is a massive time sink for us, even on powerful systems with a good Internet connection.

    Is there any way whatsoever to just force the new changeset, ignoring any conflicts, just running them all over? Our current solution is to delete the whole project and redownload it, because it's faster than trying to resolve the conflicts, and it's clearly not a good way to deal with it.

    If not, would the developers of Plastic consider adding this for the cases where a download process is somehow aborted, and results in countless directory conflicts?

    Thanks in advance.
     
  2. carlosalba1985

    carlosalba1985

    Unity Technologies

    Joined:
    Jul 19, 2021
    Posts:
    1,080
    Hi,

    In Plastic SCM you can use a cache proxy that could help to avoid downloading a big amount of data always from the remote cloud server:
    https://blog.plasticscm.com/2010/05/plastic-scm-proxy-server-explained.html

    You could even consider following a distributed workflow so you connect to a local server for most of the operations: checkin, update, merge... and you just need to connect to the cloud server to push/pull your branches:
    https://support.unity.com/hc/en-us/articles/360047015532--Workflow-Centralized-Vs-Distributed

    Regarding the reason why the update operation is aborted in the middle of the process, you could potentially undo the changes via CLI so you can then run the update again from scratch
    Code (Boo):
    1. cm unco --all
    I guess you are using the cloud datacenter that is closer to your location, right?

    Regards,
    Carlos.