calbzam

Hi, - If by default the permissions are allowed at the repository level, you will need to explicitly deny the desired permissions at the branch level. If always the same permissions are denied to make the branch readonly, I think it could be automated via CLI. - My previous comment explains the opposite scenario: where the operation is not allowed by default, if you neither allow nor deny the permissions, you can explicitly allow them at the branch level (avoiding to overwrite permissions). Regards, Carlos.

Hi, You should only need to set the permissions to explicitly allow them (avoiding to overwrite permissions). If permissions are neither allowed nor denied the opeation won't be allowed. Only a operation is allowed when the permissions are strictly allowed. Regards, Carlos.

Hello, In order to configure the permissions and avoid the need to overwrite permissions, what we normally recommend is neither allow nor deny the permissions for the specific item (eg: branch). This way, if you want to explicitly allow the permissions, you can do it without the need of overwriting them. Not sure if it helps in your environment. If you run "cm acl --help" you can check how to assign permissions to branches via CLI. Regards, Carlos.

Hi, Please check the following link where we explain it: https://www.plasticscm.com/download/releasenotes/5.4.16.700 Regards, Carlos.

Hello, According to the error, the initial merge was not able to to performed because so had some path permissions denied to your user in the repo? Is it right? The merge needed to read the full tree but your user was not allowed to do it. Regards, Carlos.

Hi, Could you clarify if after opening the Plastic window you can continuw working now using the plugin with no issues? Regards, Carlos.

Hello, Is it possible that you only pressed Update for the plugin in the Package Manager but forgot to press Import after the new version of the plugin was downloaded? Could you delete the current PlasticSCM folder in the Plugins folder and reimport the plugin from the Asset Store to see if that resolves their issue? Also please make sure they also have the Version Control package uninstalled too. Regards, Carlos.

Hi @nahuelarjonadev, - The problem is currently the locks are designed to be enabled in the central server (centralized workflow). This way, you can be sure that somebody has the lock on a file as soon as they are wortking with the central repos. - I think potentially, you could create a "before-checkout" trigger that checks in the central server if the file is locked or not (eg: parsing the result of "cm listlocks --help"). The problem is this may not be enough. You would need to check if you have loaded the last revision of the item and this is very difficult to handle considering new revisions for this item could be created in any of the multiple distributed servers. - Hopefully the new features to improve the lock mechanism can be scheduled soon. Sorry for the inconveniences, Carlos.

Hi, One option could automatize the operation via the "cm switch --help" command. I guess you are also aware of the "Browse changeset" feature, right? This way, you can browse the changeset without undoing the workspace local changes. Plastic Drive may be also useful for you: https://blog.plasticscm.com/2015/02/plasticdrive-dynamic-readonly.html Regards, Carlos.

Hi again, Could you upgrade to the very last plugin version? It should fix this problem. Sorry for the inconveniences, Carlos.

Hi, We have this other thread where we were receiving feedback about distributed/multi-branch locks: - it's in our roadmap top improve the lock mechanism to support mutiple branches or distributed environments but I'm afraid it's not currently available. I don't see how triggers would help for this workflow. You could lock an item in the local repo and then run a operation to also lock it in the central server but it won't prevent to lock the same item in a different local repo of any of your coworkers. - I'm guessing if you can use one workspace configured for a distributed workflow when you are working with source code (mergeable files) and use a centralized workflow (with Gluon or Plastic GUI) when the task involves locking some binary items. Your feedback is welcome. Sorry for the inconveniences, Carlos.

Hi, This is issue is fixed in the last public release. Regards, Carlos.

What is your Unity version? Regards, Carlos.

Hi, Even when you got this error during the installation, could you check if you can use the Unity plugin with no issues now? Sorry for the inconveniences, Carlos.

Hello, If you resolvef a merge conflict and you cheched in the changes, now you can: 1. Remove the merge result changeset and repeat the merge, this time selecting the desired contributor to keep. 2. Use the subtractive merge operation to deintegrate the changes created in the last changeset: https://www.plasticscm.com/documentation/advanced-version-control-guide#subtractive-merge Regards, Carlos.

Hi, I'm sharing it with the team. It seems like an easy fix. regards, Carlos.

Hi, If you want to be asked to enter a new encryption password, please remove the following files from all the user machines that was previously working with the cloud repos: - Server-side encryption: C:\Program Files\PlasticSCM5\server\cryptedservers.conf - Client-side encryption: C:\Users\<YourUser>\AppData\Local\plastic4\cryptedservers.conf Regards, Carlos.

Hi, You can change the encryption key but you will need first to remove all the cloud repos because you cannot use a new key if you have some cloud repos already crypted with a different key. Regards, Carlos.

Hi, We are able to reproduce the issue. I will keep you posted. Sorry for the inconveniences, Carlos.

Please remove the connection profile taht is using LDAP and only keep the SSO one and let us know if it helps. Are you using a recent Plastic version, right? Regards, Carlos.

Hi Mikael, Thanks for the update. Anyway, we are still considering your feedback regarding the Xlinks beahvior. Sorry for the inconveniences, Carlos.

Hi, Could you drive to the Preferences --> Connection Profile, and create a connection profile pointing to the cloud organization (with login via SSO). It's important you to connect in the profile via SSO (single sign-on). Please let us know if it helps. Regards, Carlos.

Hi, If you want to disable encryption in your cloud organization, we can do it for you. You can reach us via private with your details (support@plasticscm.com). But you will need to delete first all your current cloud repos where the data is already encrypted. Regards, Carlos.

Hi, The problem is the button text is not correct, right? But the functionality to mark as unresolved the conflict is properly working, right? If you are paying customer, you can always reach us at support@plasticscm.com. Otherwise, you can report your questions/issues in the public forum. Regards, Carlos.

Hi, The trigger has some environment variables taht should useful, could you cehck in the triggers guide? https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide#Serversidetriggers before-replicationwrite after-replicationwrite Environment variables In addition to the variables defined in sections Common environment variables and Server.conf variables, these are also available: PLASTIC_BRANCH The complete branch specification which is being replicated. This is the format of the branch specification: branch@rep:rep_name@server The server member will be the destination server. PLASTIC_REPLICATION_SOURCE Only available in the before-replicationwrite trigger. The complete repository specification which is being replicated. This is the format of the repository specification: rep:rep_name@server The server member will be the source server. PLASTIC_REPLICATION_ID Only available in the after-replicationwrite trigger. The id of the replication. Regards, Carlos.