calbzam

Hi Thierry, By defaulkt in Plastic the files are writable and they are not checkedout unless you explicitly do it? Are you using any specific plugin or stetting in the Plastic client? What are the steps to reproduce? Regards, Carlos.

Hi, Could you open a ticket in support@plasticscm.com for furhter details? Regards, Carlos.

If you are a paying user, you can reach us at support@codicesoftware.com and we can arrange a meeting to take a look. Regards, Carlos.

Hi, Please check the following link where we have a detailed guide for "ingore.conf": https://www.plasticscm.com/book/#_filter_pattern_files The following should work: ^*abc_[0-9].txt+$ Regards, Carlos.

- I agree that it's not very comfortable if you need to unlock tons of items via this command? But why do you need it? it's not very common. As a normal basis, undoiing the changes in the workspace will release the locks. - I'm guessing if you could pipe the guid value from the outpout of "cm listlocks --help" to the "cm unlock --help". Regards, Carlos.

Hi, Do you have a Xlink between two repos that belong to two different organizations. This is a bit weird. In order to control de access to a repo (Xlinked or not), you need to do it via permissions: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide You can deny the permissions for a group to a repo and they won't be able to access to it again. If you remove an XLinked repo and you create a workspace pointing to the parent and run an update, you will get an error message alerting the XLink cannot be resolved anymore (you can still access to the parent repo but not the Xlinked one). Regards, Carlos.

Hi, You can use the "cm find" commands to query the cloud repos and get the information you need: https://www.plasticscm.com/documentation/cmdrunner/plastic-scm-version-control-cmdrunner-guide https://www.plasticscm.com/documentation/cmfind/plastic-scm-version-control-query-system-guide Regards, Carlos.

Checking the log, it doesn't seem to be Xlink related but some queries the Plastic GUI is trying to ruin agains a not existing repo. If you create a new workspace, does the issue persist? Regards, Carlos.

Hi, If you are using an on-premises server, you may need to manually edit the locked items on the server side. If you are using Plastic Cloud edition, I'm afraid you will need to manually run the "cm unlock" commands. But If the user still has the items locked in their workspace, they can use "cm unco --help" to undo checkout on the items and this way release the locks ("Undo Changes" if you are using the Plastic GUI). Regards, Carlos.

Hi, Please attach the client logs. It seems the GUI is still running some query against a missing repo. I'm guessing if you have Xlinks. Regards, Carlos.

Restarting the GUI doesn't help? Do you have any connection profile in the Plastic GUI --> Preferences -- > Connection profile? How is this message affecting you? Regards, Carlos.

Hi, lf you are a paying customer, let's open a support ticket and we can arrange a meeting with you. The new Plastic client version is not based in mono anymore. SO you may not have a "cm.exe" but you will have a "cm" on the same path. Regards, Carlos.

Could you also review the permissions of the "client.conf" in the new path? If you pasted the "client.conf" in the client binaries folder, all the machine users will be configured to use Plastic. If you are a paying customer, you can reach us at support@codicesoftware.com and we can arrange a meeting to debug it. Regards, Carlos.

Hi, thanks for the update. If we can still help, please let us know. Regards, Carlos.

Hi, This error message appears when the client is trying to connect to a server that is not reachable. Have you installed Plastic Cloud edition over a previous Enterpise installation? What is the local server port where it's listening? Are you able to list the local repos? Regards, Carlos.

Hi, So you are using the macOS Plastic GUi for the first time against a cloud encrypted repo and you are not being requested to enter the encryption password, right? You had to enable it directly in the configuratiion files. In that case, we will try to reproduce it. Regards, Carlos.

Hi, You will need to copy the "client.conf" to the Plastic binaries folder. In macOS the path is: /Applications/PlasticSCM.app/Contents/MonoBundle/client.conf Regards, Carlos.

Hi @TimoB There is currently an issue that is preventing access with UnityID to the webUI.If you select the forgot password option, it allows you to enter a new password to be used when not using the UnityID or when it is not available.Adding one should allow you to continue. https://www.plasticscm.com/account/forgot-password Regards, Carlos.

Hi, This is a known issue. We should have a fix soon. In summary, there is not a good way at the moment to share the JIRA configuration via the Plastic global repos if you are using a cloud server. Sorry for the inconvenience, Carlos.

Hi, If you login in the Plastic desktop GUI using your Unity ID, you should be able to access your cloud repos. If the issue persists, please reach us at support@plasticscm.com Regards, Carlos.

Hi, I answered here: https://stackoverflow.com/questions/69786716/plastic-csm-make-items-private-ignored Regards, Carlos.

Hi, I think the problem is the "Incoming Changes" view doesn't perform merges. It just provides a message explaining what's happening so you can later perform the merge to unify the heads in the branch. You can disable the "Incoming Changes" view in your "client.conf" and this way, you should be able to perform the mege inside the Xlink. <EnableIncomingChanges>no</EnableIncomingChanges> If you have a Xllinked repo that is shared by two parent projects, please check the following blog post where we explain the best approach for this scenario: https://blog.plasticscm.com/2014/08/how-to-share-engine-repository-between.html Regards, Carlos.

Hi, Isn't it a blank before or after the repo name in the textbox, right? Is it happening with every repo name? Regards, Carlos.

Hi, You can force the unlock but you cannot checkin an item if it's locked by a different user. Regards, Carlos.

Hi, Could you add the following parameter to the command? --dontcheckmultihead Regards, Carlos.