Jump to content

Héber

Administrators
  • Posts

    175
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by Héber

  1. 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.

  2. 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.

  3. 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.

  4. 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.
    • Like 1
  5. 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.

  6. 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.

  7. 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.

  8. Hi Oleg,

     

    First you would need to set up some lock rules. 

    image.png

    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.

×
×
  • Create New...