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.

I've sent you an email. Regards, Carkis,

Ok, thanks for the update. If I properly understand, after removing the duplicated changesets, the repo is up and running again. Regards, Carlos.

Hi Todd,From your attached screenshot, I can see the GUI is still finding changes in the workspace. If you switch to the "Pending changes" view I guess it's also taking forever to find the changes, right?We will need to review your client logs (/Users/xxx/.plastic4/logs) to understand why It's taking so long. We can also reconfigure the "Pending changes" view to make it faster (configuring the local changes to track).Once this view is able to find the pending changes, you will be able to commit them to the repository.I propose you to get connected tomorrow Monday to review your scenario. We are located in Spain? What is your time zone?Are you evaluating Plastic?Best regards,Carlos.

Hi, The migration from SVN is via Git. We have a few blog posts with the experience from other customers that I think will help you. http://blog.plasticscm.com/2015/09/moving-from-svn-to-plastic-scm-how-we.html http://blog.plasticscm.com/2012/02/migrating-from-svn-to-plasticscm.html Please let us know if you have questions. Regards, Carlos.

Hi, The server was getting out of threads and was not responding: 2019-04-19 21:54:03,690 ActivityScheduler-20 INFO ServerStats - ACTIVE METHOD CALLS 2019-04-19 21:54:03,690 ActivityScheduler-20 INFO ServerStats - Name IP Time Thread User 2019-04-19 21:54:03,690 ActivityScheduler-20 INFO ServerStats - GetSeid 10.169.51.54 00:00:00 22 2019-04-19 21:54:03,691 ActivityScheduler-20 INFO ServerStats - GetSeid 10.169.51.54 00:00:00 23 2019-04-19 21:54:03,691 ActivityScheduler-20 INFO ServerStats - Total calls: 2 2019-04-19 21:54:03,691 ActivityScheduler-20 INFO ServerStats - 2 requests enqueued. 2 worker threads (0 free) Maybe a temporary issue when connecting to the AD to resolve the SEID? How many cores has your server? I would increase the thread number from the web admin panel: I would also upgrade the server version to the last 8.0. Regards, Carlos.

Hi, Checking your logs, I cannot see any logged info between 00:35 and 05:24 (the time you restarted the service). This log could fit with a situation where the Plastic server daemon was killed, the machine stopped... How did you check that status of the Plastic server was active? 2019-04-25 00:35:04,584 W-21 00000000-0000-0000-0000-000000000000 S-1-5-21-625948072-1123881165-1540833222-87283 CXVM-OC63 DEBUG LdapProvider - LdapSearchResult processed in 2 ms 2019-04-25 00:35:04,584 W-21 00000000-0000-0000-0000-000000000000 S-1-5-21-625948072-1123881165-1540833222-87283 CXVM-OC63 DEBUG LdapProvider - Search finished in 2 ms 2019-04-25 00:35:04,584 W-21 00000000-0000-0000-0000-000000000000 S-1-5-21-625948072-1123881165-1540833222-87283 CXVM-OC63 INFO LdapProvider - <- GetADSEIDGroups in 2 ms 2019-04-25 05:24:23,685 Main-1 INFO Daemon - Initialize Datalayer 2019-04-25 05:24:24,152 Main-1 INFO DatalayerFs.FsConfParser - JET SETTINGS: 2019-04-25 05:24:24,152 Main-1 INFO DatalayerFs.FsConfParser - basepath=/data01 Regards, Carlos.

Hi, you should be able to use the "cm hist --help" command: eg: cm history serverpath:/src/foo/bar.c#br:/main/task001@myserver:8087 Regards, 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-

Hi, I'm afraid I cannot reproduce this issue. If I create new changes under a specific Xlink (from the parent repo), then from a different Gluon workspace I can update the new content via "cm partial update" command. If you reach us at support@codicesoftware.com, we can arrange a meeting and review it with you. Regards, Carlos.

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

Hi, There shouldn't be any problem. Some of our bigger customers are using Linux servers and the clients are using Windows, macOS or Linux. The only problem I can guess is if some clients are using Linux and others using Windows related to the case sensitivity. For intsance, if you commit two folders on a Linux client "MyFolder" and "myfolder", you won't be able to download both to a Windows machine. Regards, Carlos.

Windows is a case insensitive OS while macoS is case sensitive but it's difficult to know the character that is generating this error. The log is not showing it. We can connect with the user having the problem to try to find a workaround and determine the characters generating the issue. Regards, Carlos.

If you create new changesets in the Xlinked repo, you will need to manually edit the Xlink target changeset to the last one before running the update. You don't have to run a "cm partial update" if you are using a regular workspace. You just need to edit the Xlink target and finally run a "cm update". If you want the Xlink target changeset to be automatically updated to the last, you can edit the library directly from the parent repository. This way, you won't need to manually update the Xlink target. In the following blog post, we explain how you can share a library (xlinked repo) between different projects. It may be useful in your environment: http://blog.plasticscm.com/2014/08/how-to-share-engine-repository-between.html Regards, Carlos.