Jump to content

calbzam

Administrators
  • Content Count

    1,698
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by calbzam

  1. Hi, If the certificate is not valid/cannot be verified, could you generate a new certificate from another CA? (The Plastic SCM installation also includes a self-signed SSL certificate). Regards, Carlos.
  2. Hi, If I properly understand, you can switch to most of the branches/changesets with no issues (your encryption key is properly recognized) but when you switch to a specific changeset, you are requested to enter the key again and again? It sounds like this specific changeset was created with the wrong encryption key so you current key cannot decrypt the data and that's why you are requested to enter it again and again. Is it only happening to one specific changeset? Regards, Carlos.
  3. The custom path shouldn't be relevant. We have already created an internal task to better handle this scenario. Regards, Carlos.
  4. Ups, let me try to reproduce. We should better handle this scenario. Sorry for the inconveniences, Carlos.
  5. Hi @Danny, Please check the following feature: [New] 7.0.16.2589 filetypes.conf is now used for diffs and merges to check if a file is binary or text. Until now, the filetypes.conf configuration file was only used by the "add operation" to set newly added files as binary or text. From now on it will be used to determine if a file is binary or text before running diffs or merges. Example: suppose scene.config was wrongly added as binary. You can now configure filetypes.conf to consider scene.config as text, so the right text-based diff and merge tool will be selected instead of considering the "bin type" tracked for the file in the repo. Motivations: 1. This is really useful when you are working with Plastic Cloud, since changing revision types is not allowed there. 2. Our goal is to get rid of the bin/txt tracking as metadata in the repo, and rely only on filetypes.conf. You can configure a "filetypes.conf" and this way, you shouldn't need to start a new repo from scratch. Regards, Carlos.
  6. Hi, The "Pending changes" view already supports creating custom changelists: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide Regards, Carlos.
  7. Hi. I've just synced a Plastic repo with an empty git repo in Bitbucket with no issues. So in your case, the repo content in Bitbucket is empty after the replica? Could you attach the Plastic client logs in order to find any possible error? Regards, Carlos.
  8. The most natural way would be to ignore the changes (if most of the time these changes need to be ignored) and remove them from the ignore list if you need to checkin some new changes. Also, note if you checkin the changes of a cheched-out item with no real changes, a new file revision won't be created in the repository. The "Pending changes" view supports creating custom changelists. Not sure if it would be useful in your scenario https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide Regards, Carlos.
  9. When you modify the assets via the plugin, it internally checks it out so you are sure it's not locked by a different developer. Regards, Carlos.
  10. Hi Tim, I'm afraid this kind of workflow is not supported by default. In the Plastic SCM GUI preferences, there is a comment auto-text feature that can be configured but it's not so intelligent. You can include parameters like branch name, user and date. Also, Plastic has custom triggers so you can script something custom to be run "before-checkin". https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide#Checkin Your feedback is also very welcome in our user voice page: https://plasticscm.uservoice.com Regards, Carlos.
  11. Yes, from our JIRA guide: https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide User name and Password: Specify the JIRA credentials used to log into JIRA and log the changes. If you use Atlassian Cloud, the User name must be the email address of the account, and the Password must be an API token. You can find out how to generate API tokens for your Atlassian Cloud account in their official documentation. Note that these fields can be the user credentials in JIRA, or the credentials of a different JIRA user specifically created to log Plastic SCM changes. The issue history on JIRA will display the change as coming from the user configured here. - If you are removing the "issuetracker" folder, please close the GUI first so the folder is not locked. Could you attach the Plastic client logs so we can review the error? I've just set up a JIRA cloud organization and everything seems to be working if I use the API token. If you reach us at support @codicesoftware.com, we can arrange a GoToMeeting with you to debug your scenario. Regards, Carlos.
  12. Hi, Could you open a ticket at support@codicesoftware.com including your registered account at www.semanticmerge.com? We will manually generate the trial license for you. Regards, Carlos.
  13. calbzam

    Prefabs missing

    But the changes are already committed in a changeset in the branch? And then this issuer switches the workspace to this changeset but the files are not downloaded? Not getting any specific error? My only guess is this user has configured some "cloaked.conf" rules preventing the files to be downloaded. If you have a commercial license, you can open a support ticket and we can even arrange a meeting with you to debug. Regards, Carlos.
  14. Hi, In the Plastic preferences panel, under "Other options", you can configure the "Pending changes" view to track changes only when the file content changes (but default, it only checks if the timestamp has changed). Regards, Carlos.
  15. Just as an update for this thread, after configuring the Plastic server to use "Active Directory", the users were properly resolved. Regards, Carlos.
  16. Hi, By default, all users can access the system. If you are getting a "User unknown" error, it seems that the user you entered cannot be resolved in the LDAP (or the server authentication configuration is wrong). In there was a permissions error, it would be different message. More information about how you can assign permissions in Plastic: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide We would need to review the Plastic server debug log, to better understand the error. You can reach us at support@codicesoftware.com and arrange a meeting with you to debug the issue. Regards, Carlos.
  17. You can reach us at support@codicesoftware.com. Regards, Carlos.
  18. Hi, Removing the "C:\Users\xxx\AppData\Local\plastic4\issuetrackers" folder and re-configuring the JIRA parameters in the GUI doesn't help? We may need to arrange a GoToMeeting session to review your setup. Please reach us at support@codicesoftware.com. Regards, Carlos.
  19. Hi, Are you exporting a git repo via "git fast-export" and then importing to Plastic via "cm fast-import"? It seems to be a problem with the export package. Are you exporting a public repo or a package you can share with us? Regards, Carlos.
  20. Hi, I'm trying to reproduce but it seems there is a problem with https://bitbucket.org at the moment (I can't log in) :$ Are you replicating from a Plastic repo to a Bitbucket git repo, right? Regards, Carlos.
  21. Ok, thank you very much for the update. I was not aware of theseJira's Next-Gen projects. We will need to adapt the plugin to fix your reported issues and being fully compatible with them. Regards, Carlos.
  22. Ok, so the problem is the JIRA settings are not properly saved and when you reopen the GUI the values are not there? Are you configuring JIRA for all repos or for one specific repo? I will try to reproduce. Regards, Carlos.
  23. Hi, You will need to configure your Plastic server to use your desired authentication mode: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Authenticationconfiguration Then you can create custom users and groups also from the webadmin. Once you have the Plastic users and groups, then you can assign the permissions for your users: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide Please let us know if you face any issue. Regards, Carlos.
  24. Hi, You can just replicate all your cloud repos to a local machine. But If you want to setup a backup server in your office, you will need to buy a Team edition license for that purpose: https://www.plasticscm.com/pricing Installing and configuring the hosted Plastic server is a very straightforward process: https://www.plasticscm.com/documentation/installation/plastic-scm-version-control-installation-guide Please let us know if you need more help. Regards, Carlos.
×
×
  • Create New...