calbzam

Ok, the next time it happens please consider the previous questions that should help us to debug the problem. Regards, Carlos.

Hi, - You can open a console and run "cm version". - Is the parent folder fully checked or the whole workspace content fully checked? - The next time it happens, it would be great to focus on the unchecked file and review the last changes: if it was moved by your coworker, renamed... - I guess you are not using this workspace with the regular Plastic GUI, right? - There is a command line option that you may find useful to know: [New] Gluon UI: The option '--restorefulldirs' was added to the 'partial configure' command. This option allows resetting the directory configuration in partial workspaces. Check 'cm partial configure --help' for more info. Regards, Carlos.

Hi, What is your Gluon version? Are you moving files to different folders or could you clarify the details to reproduce the issue? Regards, Carlos.

Hi, You can also manually edit the "C:\Users\xxx\AppData\Local\plastic4\plastic.workspaces" file to point the specific workspace to the new location and then move the workspace (including the ".plastic" folder) to the new location. Regards, Carlos.

Yes, the reason for this error message is the "ForceBuildNumberMatch" parameter enabled. Regards, Carlos.

Hi, The auto-upgrade feature will only work if the client and server version are not actually compatible. If they are compatible (7.0.16.X), I'm afraid that the auto-upgrade feature will not work. Sorry for the inconveniences, Carlos.

Hi, Could you also include the request in our user voice system? https://plasticscm.uservoice.com Regards, Carlos.

Hi, It seems that Unity external Merge Tool is not properly defined. Could you check if the tool is available on this path? Regards, Carlos.

Hi, There shouldn't be any performance issue you when using as many submodules as you need. We have big customers with tons of them with no issues so far. Regards, Carlos.

Hi, From our release notes: [New] 5.4.16.688 Now a full hierarchy of submodules can be added. It is possible to have repositories as follow: default/codice default/codice/plasticscm default/codice/plasticscm/windowsgui default/codice/semanticmerge Before only 1 level of submodules was allowed, but now a full hierarchy can be created, which is useful when a certain namespace policy must be enforced. All the submodules inside a given repository are stored inside the same database as the repository, actually using different table name prefixes or schemas in the case of SQL Server. Remarks: A submodule can't be moved to a different repo. It stays on the repo where it was created. A submodule can be moved "inside" a different submodule and submodule hierarchies can be freely modified just applying repository rename operations. It means you can start with default/codice default/codice/plasticscm default/codice/plasticscm/windowsgui And transform the hierarchy as follows: default/codice default/codice/plasticscm default/codice/windowsgui And even rename "codice" to "plastic-code" and then: default/plastic-code default/plastic-code/plasticscm default/plastic-code/windowsgui When you delete a submodule, you delete all the submodules inside it! Remember that delete doesn't really remove the submodule, it stays on the database and it is just unlinked from Plastic (as happens with repositories). A submodule inherits permissions from its parent submodule. When you move a submodule, the permissions from the new parent will be applied. Best regards, Carlos.

Hi Brian, No sorry, you will need to release the locks one by one with "cm unlock". Regards, Carlos.

Wow, Thank you very much for sharing! Regards, Carlos.

Hi, Yes, it should be working in both Linux and Mac. But you will need to use the command line "cm sync --help". Regards, Carlos.

Yep, we will try to find a more user friendly solution. As you know, we are adding more and more new features to the macplastic GUI. Regards, Carlos

Hi, It´s a known issue in the last Plastic version that we are going to fix. As a temporary workaround, you could enter the JIRA values, select a different issue tracker in the dropdown menu and finally select JIRA again. This way, the data should be propely saved. Sorry for the inconvenences, Carlos.

Hi Mark, Could you type the word "false" in the Gluon field? Please, review that the user who runs Unity3D is the same who runs Plastic (you probably has only configured Plastic for a specified user). Are you using Unity Pro version? Best regards.

Hi, I´m sorry, but we still don´t have an estimated release date Regards, Carlos.

Hi, Plastic has a fine grained permissions system (per server, users, repository, path...). You can configure the readonly acces to your desired user groups. https://www.plasticscm.com/features/security.html Let me know if it fits in your scenario. We can assist you with the configuration. Best regards, Carlos

Hi, Yes, If you have a wXlink pointing to Lib repo and you perform a change, a new changeset will be created in both repositories. Even if you create a new branch, this new branch will be autoexpanded as well to the Xlinked repository. Please, check this guide for more information: https://www.plasticscm.com/documentation/xlinks/plastic-scm-version-control-xlinks-guide.shtml#Chapter3:XlinkExpansionRules Regards, Carlos.

Hi, You will be happy to know that we are implementing the support to point subdirectories instead of just the root of the repository when using readonly Xlinks. Other possibilities are: - Adding to the "Cloaked list" the items you don´t want to download from the shared repositopry. Cloaked items are items that the update operation won't download by default from the repository to the workspace. http://plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide.shtml - You can also think on splitting the shared repository in different repositiories. Regards, Carlos.

Hi, I´m able to reproduce the issue when using the sync view. We are going to review it and fix it asap, but anayway using the Branch explorer or the command line, it should properly work: - Command line: cm replicate br:/main@default@localhost:8087 repoRemote@ssl://remoteServer:8088 - Branch explorer --> right-click --> replicate: Remenber that you should enter something like:"ssl://serverName:8088" in the replication dialog of the remote server (If don´t enter the protocol, you will not ble a to perform the replication). Regards, Carlos

Hi, If you configure the sync view using a hostname that is not getting the "WARNING" message (running "cm lrep"), are you still getting the error? Could you try running the "cm replicate" command instead? If a command works, the rest of the commands should also work. The client GUI is is not probably showing the warning dialogs, just the "authentication or decryption has failed" error. Regards, Carlos

Hi, I´m able to configure the same scenario. Let me guess what could be happening: - If I run a "cm lrep" using the remote IP, I get this message C:\Program Files\PlasticSCM5\client>cm lrep ssl://192.168.1.56:8088 WARNING: the secure connection hostname provided in the server certificate doesn't match the server's hostname. This means that the certificate was not issued to this hostname or that there is a network configuration problem with this host. - Certificate hostname: CN=triskelion - Server hostname: CN=192.168.1.56 If I re-run the command, the WARNING is appearing again and again. - If I run a "cm lrep" using the hostname, I don´t get this message because the certificate was issued for this hostname. C:\Program Files\PlasticSCM5\client>cm lrep ssl://triskelion:8088 1 default ssl://triskelion:8088 The same happens when configuring the sync view. You need to enter the same hostname that is stored in the certificate. If you use the IP or a different server alias, the SSL connection will not work. Summary: - Step 1: Run the "cm lrep" command and check that the WARNING message is not being shown. - Step 2: Configure the sync view using the same server name as the previous command. Regards, Carlos

Hi, Could you check if the "remoting.conf" file in both servers and clients (stored in the server and client folders), have enabled the SSL channel? Regards, Carlos

Hello, I´ve sent you an email with extended information. Previously in the post, it was reported an issue generating the certificate with the .NET SDK (I haven´t reproduced it yet). In that case, please use openssl as @gusdpr explained to generate the certificate. Regards, Carlos