Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by calbzam

  1. Hi, There shouldn't be any problem on renaming the folder with a different id as soon as you use the new id in the "cm addrep" comman to link the repo in the new server. Regards, Carlos.
  2. The installation path shouldn't be relevant. At least we don't have a confirmation from any user. If you follow the steps from my initial comment, doesn't it help? Regards, Carlos.
  3. Hi, You can force a manual file conflict (changing the file in both source and destination). This way, when you run the merge, the external mergetool with be run to solve the file conflict. If it's not running, please attach a screenshot with your external merge tools configuration. Regards, Carlos.
  4. Hi, You feedback is very welcome. We have been evaluating it but as Pablo commented, the the easiest workaround for now to get this information is creating an "after-checkin" trigger that opens a message box, pop up or similar... https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide#Checkin Best regards, Carlos.
  5. Hi @warnerjonn, Are you also affected by this problem? What is your operating system? The thing is we haven't been reported this issue from other customers so it hasn't been yet scheduled. Regards, Carlos.
  6. Hi, 1) You can just copy the current database folder content to a different folder with a different id not existing in your server(eg: "rep_57" --> "rep_58"). Then you can link the new database in your server with the "cm addrep --help" command. You will need to use a different repo name, but the repo history will be the same. 2) If you want just to clone just some specific branches, you can replicate the desired branches to a clean new repo in the same server via the sync view: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide#Chapter23:TheSynchronizationview PD: You can match the repo name and the database id with the following command. cm lrep --format=TABLE Regards, Carlos.
  7. Hi, I'm afraid the webadmin and the mergebots are running always on the server side. It shouldn't need to consume many extra resources. What are the specs of your server machine? Are you getting out of resources? Regards, Carlos.
  8. Hi, I'm testing with the last version ( I'm not sure if it's a version related issue. It would be great to schdule a meeting to debug your setup. c:\Users\carlos\wkspaces\myworkspace>cm fc --checkcontent . c:\Users\carlos\wkspaces\myworkspace\bar.bin c:\Users\carlos\wkspaces\myworkspace\foo.bin c:\Users\carlos\wkspaces\myworkspace>cm fc --checkcontent --onlychanged . c:\Users\carlos\wkspaces\myworkspace\foo.bin c:\Users\carlos\wkspaces\myworkspace>cm version Regards, Carlos.
  9. Hi, I'm afraid I cannot reproduce. If I use "--onlychanged", it shows the items that are actually changed but not showing the checked out c:\Users\carlos\wkspaces\myworkspace>cm fc --checkcontent . c:\Users\carlos\wkspaces\myworkspace\bar.bin c:\Users\carlos\wkspaces\myworkspace\foo.bin c:\Users\carlos\wkspaces\myworkspace>cm fc --checkcontent --onlychanged . c:\Users\carlos\wkspaces\myworkspace\foo.bin What is your Plastic server and client version? Has this beahvior recently started to happen ? Can we arrange a meeting to review your setup? Regards, Carlos.
  10. I'm not able to reproduce this behavior. If the file has actual changes it should appear in the output. Could you check if the file is actually changed or if just the timestamp is different but there is not real changes in the file? Regards, Carlos.
  11. HI, cm fc --checkcontent --onlychanged -R . The "--onychanged" parameter will filter the checked out items items with no changes. Is this what you need? What item types would you want to show in the output? Could you clarify? What is your goal? I mean why you don't just run "cm unco --all" to undo all the changes? Regards, Carlos.
  12. Hi, We have already schduled the task to find a way to support JIRA nextget projects. I will keep you posted. Regards, Carlos.
  13. calbzam

    Repository users

    Thanks for your feedback. if you still face any problem from the Windows client, please let us know. Regards, Carlos.
  14. We will notify you when the migration is performed. Regards, Carlos.
  15. calbzam

    Repository users

    Hi Brett, I was not aware that you were using Gluon. The Gluon workspace structure is very different from the Plastic GUI workspace and you cannot perform Plastic GUI operations from a Gluon workspace. If you plan to use both GUIs, please create independent local workspaces for that purpose. Great to know that your current client is working again and you are able to list the repos. But now there is another problem, I'm afraid that the macOS GUI doesn't have the GUI panel to configure the permissions (it can be configured via Windows GUI). From a macOS client instalation, the only way to configure the permissions is via command line. If you run "cm acl --help", you can see some examples. I understand as it's not as comfortable as using the GUI. Otherwise, we can arrange a meeting to assist you with the permissions configuration. Sorry for the inconveniences, Carlos.
  16. calbzam

    Repository users

    Hi Brett, The permissions configuration is handled directly in the Plastic GUI. It doesn't matter if you want to configure permissions for on-premises server or a cloud server. The permissions are not configured in the web panel. If you drive to the repositories list in your Plastic GUI and you right-click a repo, you can select to configure the permissions for the full server, for a specific repository and also path permissions. Once you open the permissions panel, you can select your users and groups and customize the different permissions for them. Please let us know if it helps. Regards, Carlos.
  17. calbzam

    Repository users

    Hello Brett, - Plastic allows to customize the permissions both at the server and at the repository level. You can create custom user groups in your server and assign different permissions for your internal users and external contractors. You can edit the permissions and deny the access to a specific group (for some specific repos) whenever you want. In our security guide, we explain some real case scenarios. For instance in the following link we explain how to open up a repository to a specific group. https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide#Openuparepositorytoaspecificgroup Every Plastic operation is linked to a specific permission so your security rules are very customizable. You can allow just readonly access to your repos, also allow to checkin to specific branches, to specific paths... If we can assist you with your specific scenario or you have any question, please let us know. - The cloud subscription owner is the user who manages the subscription and the payments. Every month, you will be charged based on the number of users that accessed to the cloud server this month. If a specific month, the contractors are not accessing to the Plastic server (because you denied the access or because they are not using it anymore), you won't be charged for these users. Best regards, Carlos.
  18. Hi, We are already migrating the cloud organizations to our new infraestructure cloud 2: http://blog.plasticscm.com/2020/05/announcing-new-plastic-cloud2.html In cloud2 you can use shelves. We plan to migrate all the cloud organizations in the following days/weeks. Regards, Carlos.
  19. Hi, - So you are locked and you are not able to finish the process of the merge? I haven't seen this behavior in the past If you have a commertial license, you can reach us at support@codicesoftware.com and we can arrange a meeting. - Are you using Xlinks? Meantime you can also try to run the merge via console: "cm merge --help" command. We will also need to check your Plastic client logs. - Are you using a recent Plastic SCM version? Because for we release a new months ago a new view that ease the workfllow when multuiple users are working on the same branch and avoiding to resolve merge conflicts, and this way, keeping a linear history.. http://blog.plasticscm.com/2019/10/incoming-changes.html Regards, Carlos.
  20. Hi, The problem with our current Unity plugin is their scm interface forces the plugin to checkout the file before modifying it. A workaround could be to keep these files always as cheched out so they can be edited (eg: via custom script). By the way, we are working on a totally new custom Unity plugin that doesn't have these limitations of their scm interface. Hopefully it will be released very soon. Regards, Carlos.
  21. Hi, Does error make sense to you? I mean there is a file with a long path? We released the following task some time ago: You may need to update your computer policy to make it work (see linked blog post). In order to debug this issue, it may be easier to do it from the Plastic GUI (not the Unity plugin). Once the issue is not reproducible from the GUI and you are able to to update to the last and checkin with no issues, the problem shouldn't neither be happening if you use our plugin for Unity. Regards, Carlos.
  22. We are at the moment solution to make it work in Plastic. Note that the main problem is nextgen projects doesn't support multi-line text fields so we cannot log the checkin information in the JIRA task. We are at the moment studying a different approach that should be ready in the following weeks. https://community.atlassian.com/t5/Jira-Software-questions/How-to-create-multi-line-text-field-in-next-gen-project/qaq-p/948545 Sorry for the inconveniences, Carlos.
  23. Hi, In our previous tests, there is no problem when listing the tasks from next gen JIRA projects. The problem is when you perform a cehckin in the linked branch, the information is not logged in the JIRA task because we use multiline text fields and they are not still available in next gen projects. Are you using the API token as the password? https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide Regards, Carlos.
  24. I've been sharing tour feedback with the team. Let me share our thoughts abut this topic: Regarding the writable XLinks to behave the same as readonly XLinks, it has some drawbacks. - You cannot leave loaded the changeset from any branch because then, when Plastic needs to expand the branch in the Xlink to create the change, this branch may be created from a previous changeset. And at the end of the day, the branch structure will be very chaotic and totally different from the parent repo strucuture. It would make more difficult to understand the history of the XLinked repo as it would be very different from the parent repo. Readonly XLinks don't need to perform merges (they don't need to keep the merge trazability), but this is necessary for the writable Xlinks. - Regarding to avoid the empty changesets in the Xlinked repo: In the specific scenario where the Xlink still doesn't have the branch created and you make a rebase (source in the same branch as the Xlink target), we could directly update the Xlink target instead of creating a branch with the changes from the old base . This way, you may be faking a bit the history, but you avoid the merge of the main branch to create an empty changeset that then will be propagated to other branchges. eg: 1. We have a task branch with some changesets in the parent repo involving some changes in the XLinked repo. Xlink target changeset is cs:5 2. I make a merge from main to my task branch branch (rebase). In the main branch, the Xlink target was cs:10 3. A task branch is created in the Xlinked repo from cs:5 and a merge is performed of all the changes between cs:5-10. The branch structure and behavior is the same as if you do the operation in the parent repo (a rebase to an empty branch). New proposal based on your feedback: 1. We have a task branch with some changesets in the parent repo involving some changes in the XLinked repo. Xlink target changeset is cs:5 2. I make a merge from main to my task branch branch(rebase). In the main branch, the Xlink target was cs:10. 3. The Xlink target is updated to point to cs:10 of the Xlinked repo in main. This way, the Xlinked repo won't have the real history about what you did in the parent repo (because now the merge is not performed in the Xlinked repo) but according to your feedback, you prefer to lost this history in the XLinked repo if, this way, you can also avoid propagating empty changesets. Regards, Carlos.
  25. Hi, Only the last Plastic SCM versions are avilable to install via packages: tester@ubuntu:~$ apt-cache policy plasticscm-server-core plasticscm-server-core: Installed: (none) Candidate: Version table: 500 500 https://www.plasticscm.com/plasticrepo/stable/ubuntu ./ Packages 500 500 https://www.plasticscm.com/plasticrepo/stable/ubuntu ./ Packages 500 500 https://www.plasticscm.com/plasticrepo/stable/ubuntu ./ Packages 500 500 https://www.plasticscm.com/plasticrepo/stable/ubuntu ./ Packages 500 500 https://www.plasticscm.com/plasticrepo/stable/ubuntu ./ Packages There shouldn't be any problem to configure Plastic 9 with MySQL. You need to use the same configuration ("db.conf" and "server.conf"). If you are getting any specific error, please attach the server debug log. Regards, Carlos.
  • Create New...