Héber

Hi, I'm afraid there is no easy way to tell what is going on. Most likely, something got corrupted during the process and is preventing the operation from finishing. That being said, this issue was resolved through a support ticket, and the problem was addressed by using the "git gc" command. Am I right? Best, Héber.

Hi, You could add these two entries to the client.conf located under "C:\Users\youruser\AppData\Local\plastic4" to limit the number of threads it uses and prevent flooding the router with requests. <Upload_SendDataThreadCount>1</Upload_SendDataThreadCount> <DownloadPoolSize>1</DownloadPoolSize> Best, Héber.

Hi, I'm sorry, I misread what you were using. You would need to put it as "$(hostname):8084" (or 8087, depending on your configuration). Does it make sense? Best, Héber.

Hi, Could you try setting the "Content-Type" to "application/json"? Best, Héber.

Hi, I can see that you already figured it out, but here is a guide to the API for future reference: https://docs.plasticscm.com/restapi/plastic-scm-version-control-rest-api-guide Best, Héber.

Hi, Copying the mappings folder allows you to run a GitSync operation between the same two repos without ending up duplicating the content. The folder should be here: C:\Users\youruser\AppData\Local\plastic4\sync\git\folderwiththemappings. If you have more than one folder, you can check the "git.repository.conf" file to see what Git repo it is matching. Best, Héber.

Hi, From what I have seen, it seems that WSL is not able to resolve localhost properly. Could you try instead using the hostname of the machine? Best, Héber.

Hi, What do you mean by "there is constantly changes on the workspace"? What operation is being prevented? Regarding the workspace not existing, could you check if there is a ".plastic" folder? That should mark if a workspace exists or not. Best, Héber.

Hi, The local server is listening by default on port 8087, that's why it may be failing. In any case, "local" is an alias for the servername and the port, so using "cm repolist local" should work. Is that failing? Best, Héber.

Hi, Could you try through the 8087 port? That is usually the one used by Plastic for local servers. Best, Héber.

Hi, As those files and folders have the same name and are in the same Path, Plastic cannot simply merge them. They are identified as different items (which they are). I'm not really sure what you are needing in this scenario. Would you like to compare the content of two local workspaces? That wouldn't be possible as private files belong to only one workspace and Plastic has no knowledge of them. Best, Héber.

Hi, A permission that is not Denied nor allowed is considered as not having permissions for that operation, but without explicitly preventing them from being added. When you have the denied permissions set, it takes precedence over the allowed ones and it is inherited, having to override the permissions explicitly to allow them. There are two boxes because you may not want to override the permissions for both. Or not need it. This is more common in complex user networks with thousands of users. Best, Héber.

Hi, The client needs to be downloaded as it is the only way you can handle the content as of today. The client is lightweight, around 400MB. Then you can select what content you want to download, and even work centralized with the cloud server getting only the content of a changeset (a commit in Git's jargon) to avoid downloading the whole repo. And finally, yes, you can use it with the command line tool: https://www.plasticscm.com/documentation/cli/plastic-scm-version-control-cli-guide Best, Héber.

Hi, I'm sorry you faced this issue. We are working on improving the tool so these scenarios are properly handled. Best, Héber.

Hi, Copying the reply from the other thread as it is duplicated: Best regards, Héber.

Hi, Yes, can you check it now? We had an issue with the link we were not aware of. Best, Héber.

Hi, Not all the commands have this option, but for some of them like the "cm sync" one you can specify the user and the password. You would need to use the "--user" and the "--pwd" flags followed by the proper info. Is this what you are looking for? Best. Héber.

Hi, Are those users using Gluon? Have you considered using the branch permissions instead of the path ones? The path ones would apply to the whole repo whereas the branch ones would prevent users or groups from doing the desired operations in the main branch. You can access the branch permissions window by right-clicking on a branch either in the branch explorer or the branches window. Best, Héber.

Hi Ortan, I'm afraid it is not possible. Those files are created when you are bringing content but already have files with the same name but different content. It is a failsafe measure, but in this case, it has proven detrimental. To make sure I understand what is going on, what happened is that you had a workspace, worked offline on it, and then got the content that was on the server, right? Plastic shouldn't allow you to run an update if you had new content, in any case, it should have launched the incoming changes feature. Was the workspace created from scratch, then added the content, and then run the update? Best, Héber.

Hi, You could set up an after-checkin trigger that starts the build after a new changeset is created in a certain branch: https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide Would that work? Best, Héber.

Hi, I'm afraid it is not possible. You could find all the code reviews for certain branches, find all the branches with the attributes, and then use one as the filter for the other, but there is not an out-of-the-box solution for what you are trying to do. I'm sorry for the inconvenience. Best, Héber.

Hi Oleg, First you would need to set up some lock rules. Then, whenever a user runs a checkout operation they will get the lock for that file, preventing other users from checking out and submitting that same file. Here you have more information on the lock rules: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Chapter7:Configuringexclusivecheckout(Lock) It is specified for on-premise servers, but mos information can be applied for cloud ones. Best, Héber.

Hi, What system are you using for your builds? We have integration with several continuous integration tools that should do what you are looking for. Best, Héber.

Hi, There has been a task created and it should be out this quarter, so we expect it to be addressed by the end of it. Best, Héber.

Hey, Regarding that it didn't work, do you mean that the file was still appearing as added in the pending changes view? Keep in mind that the ignore.conf only works with private files, if the files are controlled then it won't work (in this case you could use the hiddenchanges.conf one). Best, Héber.