Jump to content

calbzam

Administrators
  • Content Count

    1,679
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by calbzam

  1. Hi, I started the same clone operation this morning on my local PC. Around 7 hours running: Importing... \ 45784/138997 I'm using the "cm sync" (next time please also use the "cm" so we can get more feedback on the operation). I'm using the office network and my SSD drive. It doesn't seem to be as fast as Manu reported but it should be finishing in less than 24 hours (faster than your test). Anyway, the initial operation is what should take a longer time (this is a big repo). But after that, the sync for the new commits should be very fast. Regards, Carlos.
  2. As an update for the forum post (we have been also chatting via support email): As you probably saw in our blog, we are currently redoing the entire code review system to come up with something much more powerful, focusing on smoothing the interactions between reviewers and authors.Right now the first phase for Windows has been released, but more work is yet to be done.We'll start on the macOS side of things real soon, and our goal is to reach the current Windows feature parity before the end of 2019.Regards, Carlos.
  3. Hi, I'm afraid the redesigned webUI (including the code review support) is only available for Plastic hosted servers http://blog.plasticscm.com/2018/09/webui-web-interface-for-plastic.html Regards, Carlos.
  4. Hi, I'm afraid it's not currently configurable but it's shouldn't be very difficult to enable it https://plasticscm.uservoice.com Regards, Carlos.
  5. Hi, I'm afraid it's not possible. You will need to re-create the Xlink in order to change the writable flag. Regards, Carlos.
  6. Hi, A branch rename is not pushed during a replica operation. If you locally renamed a branch and also want to propagate this change to cloud, you will also need to manually rename the branch in the cloud repo. Regards, Carlos.
  7. Hi, It will only appear for files that are not under source control. You can only ignore private files. For controlled files, you can only add to "cloaked"/"hidden changes" list. Regards, Carlos.
  8. Hi, Are you using Plastic GUI or Gluon? If you are using Plastic GUI and there are newer changes in your working branch, you will need to update your workspace first to the last changeset of the branch (involving a merge if there are file conflicts) and then you will be able to commit your local changes. Regards, Carlos.
  9. Hi, When you right-click and select add to ignore list, you are actually adding a new rule in the "ignore.conf" file. When you add the rules, you can select to apply it only for the local workspace or not. (you can have both a local "ignore.conf" and a global "ignore.conf") Best regards, Carlos.
  10. Hi, Plastic automatically does it if you run an update operation that requires downloading a file and you already have a local private file with the same name. Plastic doesn't overwrite your local private files but renames them. Regards, Carlos.
  11. Hi, The issue seems to be with an external library that we are linking in our plugin and it happens when checking the Java version. What is your Java version? Could you try downgrading to Java 8 as a workaround? https://youtrack.jetbrains.com/issue/TW-57916 Regards, Carlos.
  12. Hi Francois, In that case, you need to use "hidden_changes.conf". Do you also have the files as checked-out? If the files are only locally changed (not checked-out), it shouldn't appear in the "Pending Changes" view. Are you using Windows Plastic GUI? I understand. It fits pretty good with the purpose of "hidden_changes.conf". Please also open the "Options" panel in the "Pending changes" view and be sure you don't have enabled "Show hidden files". The "hidden_changes.conf" will prevent you to create new revisions of this file (bu hiding your changes) but it won't prevent to download the new revisions if somebody creates a new revision of this file in the branch.Regards,Carlos.
  13. Hi Francois,If you switch your workspace with changed items (I guess you edited the preference because by default it's not possible), you can end up in a scenario where your workspace is pointing to a changeset but not all the revisions point to this changeset. You will need to update/update forced to actually overwrite your original changes.Also, you can end up with the following error: "The parent revision of the item is inconsistent with the loaded one in changeset cs:xxx"Please check the following article for more information where we explain why you have to be careful when you switch your workspace with local changes:https://plasticscmsupport.zendesk.com/hc/en-us/articles/360014970894-The-parent-revision-of-the-item-is-inconsistent-with-the-loaded-one-in-changeset-cs-xxxBest regards,Carlos.
  14. Hi, - Checkin the UE plugin repo: https://github.com/SRombauts/UE4PlasticPlugin Version 1.4.5 2019/04/27 for UE4.22:display locked files, and bay who - Gluon by default also shows the locked files and by who (not the regular Plastic GUI). Questions: 1) Are you following a centralized workflow (workspace pointing the cloud repo, not a local one)? 2) Do you have configured your custom lock rules? Regards, Carlos.
  15. Hi again, The C++ parser is very complex and it uses some Eclipse libraries. That's the reason why you need java installed. There is still a free java version, right? Open jdk. I mean why you discard Semantic Merge just because you need to install java for the C++ parser? Regards, Carlos.
  16. Hi, Semantic Merges needs java for java and C++ parser. Is this your case? If you run one of the C# samples included with the tool, you shouldn't need to install java. Could you try it? Regards, Carlos.
  17. HI Mikael, - Regarding the robustness: if you stop the process or kill the operation via Ctrl+C, it should finish the sync of the current changeset and stop the operation. Then, you should be able to re-launch it. The problem is when there is a power outage or an uncontrolled shutdown. In that case, the sync may be broken. - @manu performed the same gitsync against a local server (a few months ago) and he reports that it took just a few hours. Not sure why it's taking so long to sync to your cloud organization. Could you try installing a hosted Plastic server in your machine? If this operation is much faster, then you can push it from the Plastic local server to the cloud. Regards, Carlos-
  18. Hi, Why do you need to listen for the attribute changed in a changeset? The goal of enabling mergebot is to automatize the merges of your task branches. When the branch attribute is set to resolve, mergebot tries to automatically merge/integrate it into your baseline (before passing your tests...). Mergebot merges branches and that's why it listens to the branch attribute value. Regards, Carlos.
  19. Thanks for the update. Yes, you can directly run GitSync with a cloud repo. I can see you have opened a new thread regarding this workflow so let's monitor the operation there. Regards, Carlos.
  20. Hi, It seems that some dlls are missing. Do you have any external tool/antivirus that may be removing them? Reinstalling doesn't help? If the issue persists, you can reach us at support@codicesoftware.com and we can arrange a meeting to debug it. Regards, Carlos.
  21. Hi, If you want to change the encryption key, you need to remove all your cloud repos first to start from scratch. If you just want to be requested to re-enter the encryption key again, you can remove the following files and restart the GUI:* Client: /Users/xxx/.plastic4/cryptedservers.conf * Server: /Applications/PlasticSCMServer.app/Contents/MonoBundle/cryptedservers.conf Regards, Carlos.
  22. Hi, If you create a new workspace and run a clean update, does the issue persist? In that case, please reach us at support@codicesoftware.com including the logs. We may need to arrange a meeting with you. You shouldn't be locked in a merge even if a file was removed. Regards, Carlos.
  23. calbzam

    JIRA plug

    Hi, Just to clarify the problem is when trying to configure the JIRA plug in the webadmin panel, right? Are you following the instructions from: http://127.0.0.1:7178/devops/plugs/types/jenkins/info ? I don't see any reference to the token API. Where are you reading it? PD: The following link explains how you can configure JIRA as issue tracker for Plastic but if I properly understand this is not what you actually want. You are just configuring the JIRA plug for devops purposes. https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#JIRAintegration Regards, Carlos.
  24. You are right, the stash (we call it shelve in Plastic) is not still supported for cloud repos (only local ones). Let me understand a little bit more your workflow: - If you are creating task branches, I guess you are developers (I mean working with source code, not binary assets that then you won't be able to merge). As a developer using Plastic Cloud edition, you can also work distributed, hosting your local repos and then pushing/pulling to the cloud. I guess at the moment you are working fully centralized (your workspaces directly pointing to a cloud repo). - When you create a shelve, you are creating a temporary changeset and when you apply the shelve, you are actually running a merge of this temporary changeset with your workspace content (resolving the conflicts if necessary). That's why following this workflow you won't end up in an issue like the explained in the 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 Regards, Carlos.
  25. Hi, The problem when switching your workspace with local changes is you can end up facing problems like the following: 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 That's the reason why we don't allow by default to switch your workspace with local changes (although it's up to you to enable it). Not sure if you are aware of the "shelve" feature (also the "checkin changes to a different branch"). They can also be useful in scenarios like yours. Regards, Carlos.
×
×
  • Create New...