ollieblanks

Hey I have a few questions... Did you restart the Plastic SCM Server service after making the change to jet.conf? (I assume you have as there were 6 days between your two posts!) Can you try with a local path eg (C:\tmp\jet) to confirm whether its a permissions issue or problem with the path?

I tried lookbehind and lookahead and even an exclamation mark in case it was the same as Plastic's pattern files, but unfortunately, a negative filter does not achieve the outcome that you expect here. The options for filtering are very basic meaning wildcards (*) are as advanced as it gets. My suggestion would be to do your own conditional checking from the standard input within your trigger application. I have raised this with the Product Management team as a possible improvement to the triggers functionality. Thank you for raising it!

Hey @ben, I believe the lack of Merge button after restarting the app was a known issue with an older version that was fixed fairly recently. Can you please confirm if you are on the latest version (using the new GUI)?

Hey @imnickb, Please see our Security Guide which provides specific scenarios, including the one you describe! Hope this helps!

Can you please check that the selector at the bottom right of the Plastic SCM window is the same for both of you? For reference here is mine (/main@My 2020.3.40f1 project@Backslashgames@cloud)... Can you share screenshots of the error message you have seen?

Plastic and VPNs are compatible. Plastic and improperly configured VPNs are not compatible!

Hey @lrg_steven, Sorry to hear of your struggles. If you haven't already, please reach out to the Support team as we would love the opportunity to try and resolve this for you. (support@plasticscm.com)

Hi @Sinkea, This suggests that you do not have the "Add" permission for this file, either at path, repository or server level. For more information on permissions and security, please see here. Hope this helps!

Sorry for the delay in response! ignore.conf, only works on private files. It sounds like the log file has been previously checked in and inherently tracked by source control. To make this file private again. Manually delete the file from the workspace and then check-in the deletion, this will mean that the file is now private and will adhere to ignore.conf rules. Hope this helps!

This suggests that the license has indeed expired. Please can you log a support ticket so that we can investigate further? (support@plasticscm.com)

If you are using a sync view that means that your workspace is pointing at your local server. If you want to have a trigger fire you need to configure it on your local server. Unfortunately, this is a known limitation of using Plastic in distributed mode. Is there a reason why you are not using Plastic in centralised mode? (workspace linked directly to a remote server) Hope this helps!

hi @GardensSiobhan, As mentioned in the support ticket you logged. 1. The error message you are receiving is from the codecollaboratorclient.exe client. Are you running this operation on a Windows workstation with a configured Plastic SCM client? What is the CLI command you have run to receive this error message? 2. I believe that the whether you are on Cloud or Enterprise should have no impact on the use of this plugin. Is there behaviour that is hindering your progress? Hope this helps!

Cloud repositories are supported with the Crucible plugin. This is the task we released some time ago to support Cloud organization specs. The repository name doesn't need to include a full spec (just the repo name). [Bug] 7.0.16.2052 Crucible plugin: The plugin was unable to list repositories from cloud server. Fixed: just enter the server name in the format [code]"YourOrganization@cloud"[/code] and leave the port field empty when adding a new repository. Hope this helps!

This question would be better posed on a Unity forum. Hope this helps!

An active user is someone who makes an upload or download action on a repository. Hope this helps!

Has the workspace folder been moved or deleted?

Thank you for reporting. I will get this updated!

Hey @CliftonB, I don't think my colleague intended to cast blame on the user, but nonetheless your feedback is valid. So I appreciate you sharing it. We do understand that Plastic SCM and the terminology used can be a steep learning curve, especially for users effected by the Collaborate deprecation, and we plan to make "quality of life" improvements such as this in the coming months. If I'm not mistaken, we have already added further labels to address this very problem. If you would like to learn more about the 3-way merge system that Plastic SCM uses, then please see here. Hope this helps!

I believe this is a current known issue that we are working on. Apologies for the inconvenience. If you want to force the English version as a workaround, you can do so by setting the language value to force-en in your client.conf file. Hope this helps!

Thank you for your support of Gmaster. We have reached the difficult decision to focus our work on Plastic SCM and cease the development and support of Gmaster effective 30 March 2022. As an alternative, there are several other options for your work going forward - including GitKraken, SmartGit, and SourceTree. You may also take advantage of similar features and functionalities by utilizing Plastic SCM as your source control. You can use Plastic SCM in indirectly with a Git repository, by syncing a Git Repo with a Plastic Repo, using the GitSync feature. Hope this helps!

Does the issue persist if you include a checkin message in the box (at the bottom of the screenshot)?

Unfortunately, the History is not accessible from the diff view just yet, but it can be accessed via the Workspace Explorer and Pending Changes views. But please let me assure you, all functionality is planned to be included in the new GUI. Hope this helps!

@TapCrush, unfortunately, there is not a US West server that you can try. As the problem is likely environmental to you, it may be difficult for us to help out, but please log a support ticket with us, and we will do our best to investigate.

I suspect that the Plastic SCM Server service is not running. Can you please check this in services.msc? Does the issue persist if you download and install the latest version? (Please make sure to download Cloud Edition if you primarily use the Cloud) Hope this helps!

Sorry that you are facing this issue. If you are still having this issue please can you log a support ticket so we can do a deeper investigation?