calbzam

Hi, You can customize this value at: C:\Users\carlos\AppData\Local\plastic4\guiclient.conf <RecentWorkspacesCount>7</RecentWorkspacesCount> Regards, Carlos.

From Gluon you can also solve conflicts via merge but it doesn't fit very good with the Gluon philosophy. The artists using Gluon should be working on a single branch using locks (exclusive checkout). This way, they will never face any conflict and the workflow is very simple (no conflicts to solve). If you need a more advanced workflow for developers creating branches and integrating them via merge, they can use the Plastic GUI including all the advanced features. If you request the training, we can review in detail the Gluon vs Plastic GUI workflow to check what fits better for your needs. Regards, Carlos.

Sorry, I'm afraid the macOS GUI doesn't include this option in the right-click menu The guide is based on the WIndows GUI. If you are both using macOS, the permissions can be configured by "cm acl --help" command. Please reach us at support@codicesoftware.com and we can arrange a training session with you. Regards, Carlos.

From the Gluon GUI, you cannot configure the permissions, you will need to use the regular GUI or command line. But then the permissions will be applied to the different users doesn't matter the GUI they are using. Regards, Carlos.

Hi, we only officially support IntelliJ IDEA. There are some "descendants" that are also compatible but according to your report, Webstorm it is not Regards, Carlos.

Hi, In the following web we explain how Plastic is able to handle different complex merge scenarios: https://www.plasticscm.com/mergemachine You can especially review the details of the "change/delete" conflict that is the one you are commenting. Regards, Carlos.

Hi, In Plastic, you can configure the permissions for every operation based on your needs (doesn't matter if you use Gluon or Plastic GUI). In the following guide we explain it in detail including some real scenarios like the one you are commenting: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide If you still have some questions, we can arrange a training session with you. You can reach us at support@codicesoftware.com Regards, Carlos.

Hi, I'm afraid the task is not yet scheduled. Sorry for the inconveniences. Carlos.

As you comment, the goal is to use the environment variables to use the "PLASTIC_BRANCH" and "PLASTIC_REPLICATION_SOURCE" to select the repo and branch where you want to run the triggers. It will fire every time you replicate a branch. Isn't it the expected behavior? If you are replicating multiple branches, you could get them in your trigger script and only run the GitSync when the last branch is replicated. Regards, Carlos.

Hi, I can see you also opened a support ticket, but let me include the answer also in this thread: Yes, you crashed into 2 well-known limitations.1) Sync view doesn't see changes that are not related to new changesets. Saying it doesn't sync metadata is not 100% correct because, well, changesets are metadata after all. But, yes, basically it won't see anything if there are no new changes.We did it this way for performance reasons. It is way much faster to just check for new changesets, than it is to locate labels and so on in old ones.This is not set in stone, the goal is to improve it.The only thing I can say in our defense is that "normally" (yeah, you can argue that) new labels will go to new changesets and then will be pushed together, but sure, there will be cases when this will not happen.2) Changeset comment changes: you pushed changeset 100, then you change comment => we don't push the change to the comment. Again, performance reasons. We simply attach metadata to objects, but don't keep some sort of changelog, so detecting these kinds of changes is expensive (we keep the changelog in the form of changesets, but of course, focused on project evolution itself). Regards, Carlos.

Hi, 1. You can use the "cm listlocks --help" to review the locked files and then the "cm unlock --help" command to unlock any file as an admin. 2. You can do it via "cm listlocks --help" command. Regards, Carlos.

Hi, not sure if I properly understand. But you can upgrade your Plastic v5 to Plastic v8 keeping your previous history. The update process doesn't remove any previous database. Please let us know if you have more questions. Carlos.

- Could you check the next time the issue happens if there is a "cloudedition.token" file in your Plastic "client" folder? There could be an external tool removing it. - I guess you are not manually modifying the "client.conf" so the credentials shouldn't be lost. - In the past, we saw this problem when using the Visual Studio integration. - If you upgrade to a recent version (>8.0.16.3044), we can include the following appender in your "plastic.log.conf" in order to get more information about the issue: <appender name="ClientConfAppender" type="log4net.Appender.RollingFileAppender"> <file value="logs\plastic.clientconf.log.txt" /> <appendToFile value="true" /> <rollingStyle value="Size" /> <maxSizeRollBackups value="10" /> <maximumFileSize value="5MB" /> <staticLogFileName value="true" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date %username %-5level %logger - %message%newline" /> </layout> </appender> <logger name="ClientConfig"><level value="DEBUG" /><appender-ref ref="ClientConfAppender" /></logger> <logger name="CloudEditionConfiguration"><level value="DEBUG" /><appender-ref ref="ClientConfAppender" /></logger> <logger name="CloudEditionToken"><level value="DEBUG" /><appender-ref ref="ClientConfAppender" /></logger> Regards, Carlos-

What is your Plastic version? Are you using Plastic cloud edition? Are you using the Visual Studio package? Regards, Carlos.

Hi, There is an "after-replciationwrite" trigger you may use in this scenario: https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide#Replicationwrite You can include the gitsync command in this trigger. The trigger will be asynchronous so the push is not locked until the gitsync is finished. Regards, Carlos.

Thanks for the update!

Ok, so the internet is fast but when trying to download some data from the cloud (update operation), is it very slow? Where is your cloud data center located and where are you located? Could you run the following speed test for your data center location? http://www.azurespeed.com/Azure/Download You can also directly reach us at support@codicesoftware.com Regards, Carlos.

Hi, this setting to increase the download pool size shouldn't be related to the error. This error message ("Cannot retrieve license information from the plastic SCM server.") appears when the client can't reach the server at the moment you open the GUI. Please drive to your Preferences panel and check if the "Check Connection" is working (also review that your credentials are correct). And if you are using Plastic Cloud edition, drive to the Windows services panel, and start the Plastic Server 6 service. This is a local server to host your local repos and it may be down. Regards, Carlos.

Hi Bill, when you are running a merge, you are not always creating new revisions for the file and that's why they may not appear when viewing the file history. If you open "View history as 2D revision tree", you will see the different created revisions for this file in a 2d graph including the merges performed in the file history. Regards, Carlos.

Hi Sam, If you are a customer, please always reach us at support@codicesoftware.com for a faster answer. There shouldn't be cached information in the GUI client after restarting it. If you drive to preferences, are you able to "check connection" with no issues? Are you configuring your client entering the server name (or IP)? Could you send to our support email your client log? C:\Users\<user>\AppData\Local\plastic4\logs\plastic,debug.log.txt If you re-enter the line in your client host file, doesn't it help? Regards, Carlos.

This is the workspace selector format. You can open a console in any if your workspaces and run the following command: cm showselector --help Regards, Carlos.

Hi, sorry it's not clear in the documentation. You can copy the selector from any of your workspaces. Let me show you some examples: repository "default@localhost:8087" path "/" label "v1.0" repository "default@localhost:8087" path "/" smartbranch "/main" changeset "11" Regards, Carlos.

And can you confirm that this IP in the error belongs to the Plastic server, right? If you reach us at support@codicesoftware.com, we can arrange a gotomeeting session to debug the issue with you. Regards, Carlos.

Hi, - Regarding the error, we are already handling it via support ticket. We will update this thread with all the details when we figure out the problem. - Regarding the feature request, it's the same you are commenting here, right? We can continue reviewing it in this other thread. - If you open the "Branch Explorer" view, you can navigate through the different changesets of the branch and then run a diff for any of them in order to see the different files modified in this changeset. You can also open a diff panel from the "Branches" view or also from the "Changesets" view. Please let us know if you still miss something. Regards, Carlos.

Hi, I can see you a configuring your client with the server name and then the branch explorer query is trying to reach the server IP. I guess this IP belongs to the server and it's reachable. If you open a console and run "cm lrep", can you list the repos? If you create a new workspace for this repo and then open the branch explorer, does the issue persist? Regards, Carlos.