Jump to content

ollieblanks

Administrators
  • Posts

    268
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by ollieblanks

  1.  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!

  2. 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)...

    image.png

    Can you share screenshots of the error message you have seen?

  3. 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!

  4. 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!

  5. 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!

  6. 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!

  7. 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!

  8. 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!

  9. 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.

    image.png

    But please let me assure you, all functionality is planned to be included in the new GUI.

    Hope this helps!

×
×
  • Create New...