Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Héber last won the day on August 10

Héber had the most liked content!

About Héber

  • Birthday March 14

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Héber's Achievements


Apprentice (3/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. Hi Peter, Using the jet.conf file is the way to go. With it, you can specify where the repositories should be created. A new "jet" folder will be there with the repos inside. If you create a new repo, a new folder inside the jet one should be created named "rep_X" where the X stands for the number of the repo. Keep in mind that it will start creating them there, not move the old ones. What version are you using? I guess this is a cloud edition, right? Can you share your jet.conf file? Best, Héber.
  2. Hi Alan, Can you share the version of PlasticSCM, Unity, and the Unity plugin you are using? Best, Héber.
  3. Hi, Are you working centralized or distributed? I'm afraid that if you are working distributed, then you won't be able to close changes with the comments. Aside from that, they are closed when checking in. Best, Héber.
  4. Hi Scott, Got it, I'm sorry for the late reply. We will keep going on that one and then update the forum thread with the answers. Best, Héber.
  5. Hi, In this blogpost it is explained how to do it: https://blog.plasticscm.com/2019/10/improving-new-plastic-code-review-part-ii.html Keep in mind that you need to be working centralized for the option to close them that way. Best, Héber.
  6. Hi Pablo, I'm sorry for the late reply. You can set a group as the owner of the server and all the members of that group will be considered owners. To do that you first need to create the group and then select the option to change the owner on the bottom side of the repository server permissions screen:   The repository server owner has nothing to do with the OS user used to start the server, it is just who has always permissions for everything in the server. Best, Héber.
  7. Hi, I'm really sorry you are facing all these issues. Could you reach us at support@codicesoftware.com so we can try to set up a meeting to debug the environment? Best, Héber.
  8. Hi, Could you reach us at support@codicesoftware.com and send the "plastic.debug.log.txt" file that you should have under "C:\Users\username\AppData\Local\plastic4\logs"? Best, Héber.
  9. Hi Dan, It means that you have not entered the encryption key for the server, or that you have not configured your config files for it. I guess your organization shows the "encrypted: Yes" label in the cloud dashboard? Best, Héber.
  10. Hi, I'm glad to hear you can keep working now. If you face something similar again, please reach us at support@codicesoftware.com and we will try to help you. best, Héber.
  11. Hi, Could you reach us at support@codicesoftware.com to review this particular scenario? I may need to ask you for some specific information you probably don't want to share here. Best, Héber.
  12. Hi, As an update, we are trying to find a spot in the roadmap to have them this year. Best, Héber.
  13. Hi Erik, As talked through e-mail, I'll paste here the answer in case it helps anyone else: Best, Héber.
  14. Hi, Got it, I'll share it with the team. Regarding Plastic checking it out automatically, by default, PLastic can't do that. If you are using a plugin, it is probably the plugin the one checking it out. Another option would be if you are running a merge or an incoming changes operation. In those scenarios, Plastic does check the file put. Best, Héber.
  15. Hi Galen, I'm sorry for the late reply. No, I'd say this is not the expected behavior. Let me share it with the team and double-check it. Best, Héber.
  • Create New...