Héber

Hi, I'm not sure I'm understanding what you are trying to achieve here. If it is only the find thing, then you can also add the entry to check the attribute and attribute value, but I'm not sure if this is what you are looking for or not. Could you give us more details? What is the final goal? Best, Héber.

Hi, Do you get those errors when trying to checkin? I'm guessing if it could be that we are not finding the changes after the rename and that's why it fails. If you run the check-in in steps, does it work? (first the changed, then the moved, and so on). Best, Héber.

Hi Jashan, Do you recall reverting that file to a previous revision? Could you check which one is being loaded? It should be the one in bold. Could you open a new ticket at support@plasticscm.com with that information and referencing this post? Best, Héber.

Hi, First of all, what we would need is to run a "cm iostats yourorganization@cloud" to check the actual speed that you are getting. Based on those results we can try to ascertain why it is being that slow. Could you share that information? Best, Héber.

Hi, Right now, the GitSync tool goes through the mapping file for GitLFS and downloads the content from there too to bring it to Plastic and vice versa. But there is a flag to avoid syncing that part. Can you try running the GitSync command from the command line and adding the "--skipgitlfs" flag? Would that be an option? Best, Héber.

Hi, There are some tweaks we are working on before being able to upgrade those libraries and the team is currently working on it. Hopefully we have a fix soon. Best, Héber.

Hi Luke, I'm afraid not yet. It is in the backlog, but still not developed. I'm sorry for the inconvenience. Best, Héber.

Hi Stephen, I understand your frustration with this. The problem is that branches are an entity by themselves in Plastic, and operations can be run against them. In fact, a workspace can be pointing to an empty branch (although it will be loading the content of the parent changeset) thus the need to show in the selector the branch without the changeset. I agree that the usability here could be improved, but there is no way at the moment to get all the information with one command. I'm sorry for the inconvenience. Best, Héber.

Hi, If the workspace was properly created there is no reason for it to be missing. We would need to check every case in particular as it can be a permissions issue, or some other problem while creating it. That being said, this is not a common scenario, let us know if you face it again. Best, Héber.

Hey! This is Héber. Can you try creating a "plastic.selector" file in that location with the following content replacing the repo and organization name with yours? rep "repponame@organizationname@cloud" path "/" smartbranch "/main" changeset "0" Once that is sorted out, could you run an update operation? Best, Héber.

Hi, As an update, updating the tool fixed the issue. Best, Héber.

Hi, Since version 10 the remoting.conf is no longer the file in use for the connections. You need to use the network.conf and configure it there just adding the protocol and the port. Best, Héber.

Hi, In this case, I think the only option would be to select the file you want to revert, browsing the history by right-clicking on it and selecting the appropriate option, and finally the option to revert to the selected revision:  Unless the changes you want to revert were made in changesets separately, which I don't think is the case. Best, Héber.

HI, Can you check that your workspace is pointing to the cloud server's repo? My guess is that at least one of you is working distributed without pushing the changes, so they are not being sent to the server. here you have more information on how to work centralized: https://www.plasticscm.com/documentation/cloud-edition/plastic-scm-version-control-cloud-edition-guide#WorkcentralizedwithPlastic Best, Héber.

Hi, Yes, it is supported. Let's try this: Open the regular PlasticSCM GUI. Go to "other actions" and then "sync repositories". Create a new sync view and set the local repo as the source one and the cloud one as the destination one. Push the branches with the "push visible" option. Go to the repositories view. Set the cloud server in the top bar and then search for the cloud repo you just synced. Right-click on the latest changeset. Select the "switch workspace to this changeset" option. With that, your content should be in the cloud now and your workspace pointing to that repo, so you don't need to run the sync operations anymore. Best, Héber.

Hi, Can you confirm that you are working against the cloud server? You may have created it for the local one that is installed with each Plastic cloud edition. Here you have a guide that may help you: https://www.plasticscm.com/documentation/cloud-edition/plastic-scm-version-control-cloud-edition-guide Best, Héber.

Hi, Azure added some limitations to repos bigger than 5GB, so in order to sync them, you need to use the web importer. I think this might be what is happening to you. Here you have more info: https://docs.microsoft.com/en-us/azure/devops/repos/git/limits?view=azure-devops We are working on having at least a proper message for the issue, but I'm afraid it is out of our hands having it working. Best, Héber.

Hi, For the recent Ubuntu version where the libgnome2 library was deprecated, we recommended users grab the packages from the Ubuntu18 - Bionicle repos. That one should be the one you need to install. Regarding PlasticX, it is in Alfa, so if you want to use it, that's perfectly fine. Most of the team uses it, but we end up lacking some functionalities. It should give no particular errors, but keep in mind that it is not even a Beta yet, expect missing features and bugs. Aside from that, I can't tell you whether to use it or not. Best, Héber.

Hi, I'm afraid Arch Linux is not supported.You can find the binaries for the server here "https://www.plasticscm.com/download/10.0.16.6038/linux" but not for the client, as you can only accept the EULAs with the installers or packages.Furthermore, if you were to use the client ones, I cannot guarantee that the GUI is going to work fine.I'm sorry for the inconvenience. Best, Héber.

Hi, I'm afraid Arch Linux is not supported.You can find the binaries for the server here "https://www.plasticscm.com/download/10.0.16.6038/linux" but not for the client, as you can only accept the EULAs with the installers or packages.Furthermore, if you were to use the client ones, I cannot guarantee that the GUI is going to work fine. Best, Héber.

Hi, No, there is no maintenance planned for today. We have experienced an issue on the UEeast server, but it should be fixed by now. I'm sorry for the inconvenience. Best, Héber.

Hi, Are you working with an on-premise server installed in your machine? If you are not, then the reason is that the address is only valid for that type of server. If you are using a cloud edition then the address should be just "local" for working distributed or "yourorganization@cloud" for working centralized. Best, Héber.

Hi, If you are working centralized then you need access to the server in order to check the file out, as it would try to get a lock on it. If you don't have access to it, I'm afraid you can't checkout the file. If you are working distributed, make sure that the workspace is pointing to the local server. Best, Héber.

Hi Peter, Using the jet.conf file is the way to go. With it, you can specify where the repositories should be created. A new "jet" folder will be there with the repos inside. If you create a new repo, a new folder inside the jet one should be created named "rep_X" where the X stands for the number of the repo. Keep in mind that it will start creating them there, not move the old ones. What version are you using? I guess this is a cloud edition, right? Can you share your jet.conf file? Best, Héber.

Hi Alan, Can you share the version of PlasticSCM, Unity, and the Unity plugin you are using? Best, Héber.