calbzam

Hello, This is a false positive. We already reported it to Microsoft and they concluded that it's not actually malware. We will double-check it because it shouldn't be happening now. Sorry or the inconveniences, Carlos.

Hi, Are you aware of the Xlinks feature? https://www.plasticscm.com/documentation/xlinks/plastic-scm-version-control-xlinks-guide I think it fits very good with the scenario you are describing. If the libraries are shared between different projects, we have a blog post explaining this use case: http://blog.plasticscm.com/2014/08/how-to-share-engine-repository-between.html Regards, Carlos.

HI. There is a parameter where you can configure it in the "C:\Users\carlos\AppData\Local\plastic4\guiclient.conf" fileeg: <RecentWorkspacesCount>10</RecentWorkspacesCount> Best regards,Carlos.

Hi, There shouldn't be any problem upgrading to Plastic 8.0. The 5.4.16.X clients will be still compatible with the 8.0.16.X server. Anyway, we also recommend upgrading the clients. After upgrading, you can switch to Jet using the web admin panel. You can more details regarding Jet in the following link: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#HowtobackupandrestoretheJetbackend Do you have a license supporting Plastic 8.0, right? If you have more questions, please let us know. Regards, Carlos.

I think something like the following would also work: cm find review where id=123 --format={comment} We need to add "comment" as an output option. We would appreciate if you also add the request to our user voice system: https://plasticscm.uservoice.com

Great! Thanks for the update.

Hi Andrew, I'm afraid that distributed locks for the cloud is not supported. It's in our roadmap to include it (we have some good ideas) but I'm afraid this feature is not still scheduled. All you feedback is very welcome. If you want to use locks (I guess with Gluon?), we recommend you to follow a centralized workflow pointing your workspaces directly to the central server. Regards, Carlos.

Hi, I can see the following error in the log: "The specified repository couldn't be found: Passpartout PC". The GUI is still querying the removed repo. I guess the workspace is not poin ting to this repo anymore, right? There should be any view or configuration trying to reach this removed repo. Not Xlinks? If I properly understand, the issue is not happening at the moment. Regards, Carlos.

Hi @Mikael Kalms, the issue should be already fixed in your dashboard. Regards, Carlos.

Hi, Making a bit longer the left panel, the GUI seems to be at least usable. Could check if it helps? Regards, Carlos.

Could you let us some more details of your workflow? Do you have multiple developers working on the same branch? I guess you are using Plastic GUI instead of Gluon? Regards, Carlos.

Hi, I'm afraid the update-merge operation is not available if using cloaked rules: "Update-merge" is described as follows: If changes in the range [12-16] do not collide with the changes the developer made based on "11", then Plastic is able to do the following: it will download the new changes (not setting them as checked-out) and will effectively make the "checkouts on the workspace" depend on cset "16" instead of "11": It is important to highlight that this will only happen if the changes in [12-16] DO NOT collide with the changes the developer made based on "11", otherwise a regular merge will be launched. Now: there's a caveat to this behavior -> we do not let the update-merge run if there are cloaked rules in the workspace. We added a stronger restriction on release BL578. So, from BL578 update-merge doesn't work if there are cloaked rules in the workspace. Regards, Carlos.

Hi, Plastic doesn't have specific pluginfor this tool but it will track all your changes thanks to the transparent scm feature: https://www.plasticscm.com/features/transparent-scm Plastic SCM detects all the actions you did and displays them together so you can quickly check them in and get back to coding. If you are working with binary files, we recommend you to follow the lock (exclusive checkout workflow) and using Gluon. This way, you will avoid conflicts with files that are not mergeable and you will keep the workflow very simple (Gluon is a very easy to use tool). https://www.plasticscm.com/gluon You can book a free training session with us in the following link to give you some more workflow recommendations and help you with the setup: https://calendly.com/codicesupport/60min Regards, Carlos.

Yes, I'm afraid at the moment "comment "is not available in the format field. We could include it as a feature request. Regards, Carlos.

If not moving the ".plastic" folder, you are not actually moving the workspace but creating a new one on a different location. But as you are moving the workspace content, it won't need to be downloaded again (only the workspace metadata is recreated in the new path). The proper way to move a workspace is via command (not manually). cm cwk --help But the user reported a problem with this command so we were trying to find a workaround. Regards, Carlos.

Great! Thanks for the update. From the server web admin panel so you should be able to reset the repository server owner so you can recover if deny the permissions to ALL_USERS by mistake. Regards, Carlos.

Hi, The problem may be that you need to re-run the merge operation from the "branch explorer" view in order top finish solving the merge conflicts and only at this point to you will be able to checkin your changes. If you do not find a workaround, please reach us at support@codicesoftware.com and we could arrange a GoToMeeting with you. Regards, Carlos.

Hello Donald, We have a few resources where we explain this scenario and how and why Plastic is handling it this way: - "Conflicts during checkin – working on a single branch" section where we explain detail what is an update-merge operation in Plastic: https://www.plasticscm.com/book/#_conflicts_during_checkin_working_on_a_single_branch - Why checkin asks to update first? --> In this blog post, we start explaining what is merge tracking and why Plastic uses by default per-changeset merge tracking. It's very important you review the "Conflicts on main – why does new files come to my workspace?" section to properly understand this behavior http://blog.plasticscm.com/2018/02/why-checkin-asks-to-update-first.html Note that is blog post is a bit old and still mentions that Gluon is not able to handle merges. Please avoid this part as some months ago we improved Gluon to solve file conflicts. - What is the recommended workflow for binary files in conflict? If you are using Gluon, we recommend using locks. This way, you can avoid conflicts with not mergeable files (binary). https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Chapter7:Configuringexclusivecheckout(Lock) I know that some of these Plastic concepts are not trivial and I would like to offer you a GoToMeeting session where we can review and focus on your specific cases. You can reach us at support@codicesoftware.com to schedule it. Regards, Carlos.

Hi Tomar, Checking the "cm find" guide: https://www.plasticscm.com/documentation/cmfind/plastic-scm-version-control-query-system-guide#Codereviews You can use "comment" in the filtering options for the query. Is this what you need, right? Regards, Carlos.

Hi, This message appears when you are trying to commit some changes but a merge operation is not finished. You can re-run the merge operation from the branch explorer to finish solving the conflicts or you can just undo the changes. If your pending to commit changes involve merge changes, you need to checkin all of them. You cannot partially only checkin some merge changes. Regards, Carlos.

Hi, Thanks for reporting. Let me share with the team. I can also reproduce the issue. Regards, Carlos.

Hi, I will try to push the task but I'm afraid it's not yet scheduled. Good to know that you at least found a workaround via GitServer. Regards, Carlos.

Hello, this recalculation is somehow related to the Plastic plugin? I mean if you disable the Plastic integration, isn't it still happening? I think this hash recalculation... is directly handled by Unity when it considers necessary. We could open also a thread involving them to clarify. I think we haven't been reported a similar issue before. Are you evaluating Plastic? Regards, Carlos.

Ok, sorry, I fully understand now. The lock (exclusive checkout) was designed to avoid merge conflicts on binary files (impossible to be merged). That's why in this case the lock is not applied. You can always delete a file, even if it's locked by a different user (but you can't checkin new changes for this file). Gluon only supports file merge conflicts (via mergetool) while the Plastic GUI fully supports advanced directory conflicts like the one you are mentioning. In Gluon you will see a panel like the following: Regards, Carlos.

Hi, We recently sent a poll to users to ask for the new features to be implemented. Did you receive it? Deleting changesets in the cloud is on the top and we will start working on it very soon. Regards, Carlos.