Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by calbzam

  1. Hi, Could you reach us at support@codicesoftware.com with the "plastic.debug.log.txt" in order to review the error details? Regards, Carlos.
  2. Hi, The thing is when you are undoing changes, Plastic internally promotes them first to checkout and that's why the trigger is invoked. We should protect this scenario to avoid the "before-clientcheckout" triggers to be run in this scenario. Sorry for the inconveniences, Carlos.
  3. Hi Andy, Please check the following blog post and let us know if you still have any question: http://blog.plasticscm.com/2019/03/connect-unity-cloud-build-to-plastic-cloud.html Regards, Carlos.
  4. - If you try to start the "Plastic Server 6" service, is it able to run? Could you attach your "plastic.debug.log.txt"? - According to the "cm licenseinfo" command, your trial license is expired. So it seems your server is running but still with the expired license. - Do you have a "plasticd.token.lic" in the "server" folder? In that case, please remove it. - Are you evaluating Plastic SCM? In that case, you can reach us at support@codicesoftware.com and we can arrange a meeting to debug the issue. Regards, Carlos.
  5. This is the same behavior using Xlinks or not. The "cloaked.conf" rules are applied only if the file is already in the workspace before you run the update. If the "cloaked.conf" file is downloaded during the update from the repo, I'm afraid the rules won't be applied during the initial update (but they will do the next time because the "cloaked.conf" will be already in your workspace). Regards, Carlos.
  6. Why do you say the "Plasticd.exe" is not working? I can see the server is up and running but the license still appears as expired, right? Is this correct? Please review that you don't have a license token: "plasticd.token.lic" still pointing to the old license. Please also run the "cm licenseinfo" command and attach the output. Regards, Carlos.
  7. Hi, If I properly understand, C is the parent repo that has Xlinks pointing to repos A and B. I'm able to create some cloaking rules in the C repo applied to the Xlinked content. I can do it via GUI --> right-click --> Add to the cloaked list. Then, If I create a new clean workspace pointing to C and before updating, I copy my previous "cloaked.conf", these files are not downloaded to the workspace. Remember that these cloaking rules apply to Xlinked content. In summary, I'm not able to reproduce your issue. Are you using the Windows Plastic GUI? Could you attach some screenshots and your "cloaked.conf"? Regards, Carlos.
  8. Hi, "plasticd.exe" is the Plastic server and by default, the Plastic server is run via Windows service. Why are you trying to manually run this .exe? Could you let us know the specific steps you are following (commands, screenshots and error messages would be helpful). Regards, Carlos.
  9. Great! Thanks for the update
  10. Hi, If you want to allow switching to a different branch with pending changes (even if they are ignored in the "Pending changes" view), you can configure this behavior in the GUI "Preferences" --> "Other options" panel. You can "allow", "allow showing a warning" or "don't allow". With this warning, we try to avoid errors like the one we explain in the following article: https://plasticscmsupport.zendesk.com/hc/en-us/articles/360014970894-The-parent-revision-of-the-item-is-inconsistent-with-the-loaded-one-in-changeset-cs-xxx Your feedback is welcome. Regards, Carlos.
  11. Hi, You can use a sync view to clone a repo: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide#Chapter23:TheSynchronizationview Regards, Carlos.
  12. Hi, I'm afraid this is a known issue. We already have a task to fix it and to improve the API REST. We will let you know as soon it's released. Sorry for the inconveniences, Carlos.
  13. Hi, we designed the help system to not only help newcomers but also to prevent frustration to experienced users. The system is able to detect frustration scenarios such us empty views, unused features and so on. Right now there's no way to disable the system but notice that those cards you choose to hide will not appear again.Can you please get feedback from your users about the messages that shouldn't appear? We can improve the system with their feedback. Regards, Carlos.
  14. Hi, I don't fully understand your question. If you need to configure a Plastic client, you can do it via GUI preferences or via console running "clconfigureclient". Regards, Carlos.
  15. Hi, If you are the Plastic server admin (or if you don't have denied permissions for any specific repo), you can get the full repo list by running: cm repository list Regards, Carlos.
  16. Hi, In Plastic, there is not such a concept. When you list the repos, you will see all the repos where you have permissions enabled. I mean, if some repos are not appearing in the list, it is because you don't have "view" permissions to see them. Otherwise, you will have access to all of the repos. The only way to handle repo access is via permissions: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide Regards, Carlos
  17. Hi Scott, We have just released a new task that should be helpful in scenarios like yours: [Bug] All platforms - Plastic, Gluon: We improved the behavior when you have local changes and the changeset loaded in your workspace is deleted by a different user. Before these improvements, this meant that you got stuck: at that point you were unable to checkin, shelve or undo your local changes. We modified the client behavior to enable you to undo your local changes, letting you out of that loophole. Shelving or checking them in will still be unavailable, as they wouldn't have a parent changeset. The 'undo' behavior will be slightly different depending on the client you use: Gluon will always allow you to undo the local changes. If the original contents aren't available anymore, the head contents of the current branch will be used instead. Plastic, on the other hand, will notify you about the inconsistency and then ask you for confirmation to undo all your local changes and update the current workspace. Regards, Carlos.
  18. When you install Plastic, there is always a "default" repository. You can remove it if you don't need it anymore. Regards, Carlos.
  19. Hi @SDSChad, When you run an initial Gitsync operation, one the repos involved always need to be empty. The problem is: In the Machine B, you don't have any previous GitSync mappings. This machine is not aware of the previous GitSync performed in Machine A. When you sync the git repo, the commits are duplicated into your Plastic repo (at the end of the day breaking the repo). Machine B doesn't know that there was a previous sync. You will need to manually remove the duplicated changesets. Summary: - Always perform the GitSync from the same machine. - If you want also do it from a different machine, you will need to use a clean new repo for the initial sync. These ways, the mappings will be also generated in the new machine (and not changesets will be duplicated). Regards, Carlos.
  • Create New...