Jump to content

manu

Administrators
  • Posts

    4,598
  • Joined

  • Last visited

  • Days Won

    130

Everything posted by manu

  1. I'm happy to share we support now Github LFS since version 9.0.16.4511. Please check the details at the release notes: https://www.plasticscm.com/download/releasenotes/9.0.16.4511?term=lfs
  2. Hi Marco, the only option right now is the one Pablo mentioned up there: I'm sorry I can't offer something better. "Trimming the data" repository consists in running the "cm archive" repository to preserve the history but remove the data. So the steps would be: 1. You identify the repository is very big. 2. Pull the cloud repository to a local repository. 3. Create a new workspace to work with the new pulled local repo, you don't need to update the workspace, just create a new one empty. Open a command line tool to the new workspace path and run the following command to remove all the files greater than 300MB that are not the HEAD revision: cm find "revs where size > 30000000 and parent!=-1" | cm archive -c="volume00" --file="volume00" - You can obviously add a grep command in between the find and archive commands to grep certain file extensions or certain directories only. 4. Push the local repository to a new cloud repository 5. Delete the old-big-repository. 6. Start using the new cloud repo until it gets big again. Finally. have you considered removing the baked files from the repository and bake&use them during the CI step? @Marco this is a way to do it, we are aware there should be a better way to do it.
  3. Hi @Marc S I have just tested it and it work fine for me: I changed the display.options.show_parent_to_child_arrows to true at the $WKS_PATH\.plastic\plastic.branchexplorer file. You are right. We didn't make it a preference because it's not that common to change the arrow direction.
  4. Hi @Marcoand @JEP I want to let you know it's in our backlog and we want to get it implemented. Unfortunately we didn't have time to spend on it yet.
  5. Hi @argb32! if you want to use the status command in combination with the check-in command you need to use the following parameters: d:\wkspaces\adventure_ivan>cm status --short --compact --fullpaths d:\wkspaces\adventure_ivan\Assets\Animators\Environment.meta d:\wkspaces\adventure_ivan\Assets\Scenes\Market.meta d:\wkspaces\adventure_ivan\Assets\Items.meta d:\wkspaces\adventure_ivan>cm status --short --compact --fullpaths d:\wkspaces\adventure_ivan\Assets\Animators\Environment.meta d:\wkspaces\adventure_ivan\Assets\Scenes\Market.meta d:\wkspaces\adventure_ivan\Assets\Items.meta
  6. Hi @argb32, the problem here is the checkin command is receiving * as the list of file to be checked-in. The * will translate into every single file of the directory. Some of those are not changed and the command fails. If you want to let the command to find all the changed files then remove the *, the command will recursively find those for you. Let me give you an example: d:\wkspaces\adventure_ivan>cm status /main@adventure@catacroquer@cloud (cs:128 - head) Changed Status Size Last Modified Path Changed 204 bytes 31 seconds ago Assets\Models.meta Changed 204 bytes 27 seconds ago Assets\Scripts\Editor.meta Changed 2.68 KB 8 seconds ago Assets\Scripts\Editor\DataPersistence\DataResetterEditor.cs d:\wkspaces\adventure_ivan>cm ci .\Assets\ --all --applychanged The selected items are about to be checked in. Please wait ... - Checkin finished 3.08 KB/3.08 KB [##################################] 100 % Modified d:\wkspaces\adventure_ivan\Assets\Models.meta Modified d:\wkspaces\adventure_ivan\Assets\Scripts\Editor.meta Modified d:\wkspaces\adventure_ivan\Assets\Scripts\Editor\DataPersistence\DataResetterEditor.cs Created changeset cs:129@br:/main@adventure@catacroquer@cloud (mount:'/')
  7. Hi @Bubu101! I'm sorry you are facing this problem. I'm wondering if the file path is too large for windows to manage it. Although the common error for that issues is "Filename is too long". Just in case, can you please rename the "MM_VestAccessories_Modern_Military_Gun_Holister_2_Pbr_MetallicAlpha.png.meta" to something shorter? Rename also the ".png" version of the file. Then, try again to checkin. Can you please run the "cm support bundle" command from the command line, and attach it? I'll review it for issues. Best, Manu.
  8. Hi @Audacity I recommend you to use the "cm sync" command to import a P4 depot path, and all its history, to a Plastic SCM repository. We call it "p4sync". Please find a complete guide of the Perfoce "cm sync" command here: https://plasticscmsupport.zendesk.com/hc/en-us/articles/360023787873-P4-Sync-How-it-works Also, check the link below, it explains the main differences between P4 and Plastic, and why Plastic SCM is better and faster. https://www.plasticscm.com/alternative-to-perforce Best, Manu,
  9. Hi John! First thing is to prevent the "/main" branch modification by those users. You can right click the "/main" branch -> permissions -> Add the EXTERNAL_DEV group and deny the "ci" permission. From that moment they will not be able to touch the /mian branch. This example goes a little bit further: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide#Preventchangesonabranch it presents more operations such us creating new branches which is too much for your case. You said you tried to deny all the permissions, but for which object? Can you give me more information?
  10. manu

    Jet backup on windows

    Hi Dale! I believe I answered this one using the Zendesk support, but just to let the community know my answer, here it goes: Best, Manu.
  11. Sorry about that. We initially did it because we had a lot of SPAM attacks but you are right, we are going to make it easier. Again, sorry for the inconvenience.
  12. Hi @ScottP! The bad news is you can't recover a deleted changeset, it's gone. Good news is you have a backup of the changes, so let's do the following: You mentioned you did a change on a file after removing the changeset, so you workspaces has changes, you can undo the change or shelve it to avoid losing its content. Then, once you have the workspace clean, place the files you copied outside the workspace (as a backup) back inside the workspace, open the pending changes view and check the change in. Hope it makes sense. If you still have questions don't hesitate to contact us again! Best, Manu.
  13. Try this! cm cat serverpath:/Assets/_Complete-Game.meta#cs:2@UG-MK1@localhost:8087 --file=_Complete-Game.meta I do recommend you to use "--file" instead of dumping the stdout, you might have issues with the file encoding and strange symbols the bash can't handle and the --file parameter masters it.
  14. manu

    Update groups

    Hi! Don't worry here to help everybody :) Yes! There's another way although it's a manual process, I'm not sure if it will be useful if you are looking to automatize it. You can use the Plastic SCM WebAdmin interface to manage the groups: You can type "umtool.exe --help" to get the command usage and check examples. C:\WINDOWS\system32>umtool --help These are available commands. You can either use long commands names or short command names. Long name Short name ------------------------------------ addgrouptogroup agtg addusertogroup autg changeuserpassword passwd creategroup cg createuser cu help hlp listgroups lg listmembersfromgroup lmfg listusers lu removegroup rmg removegroupfromgroup rmgfg removeuser rmu removeuserfromgroup rmufg renamegroup rng renameuser rnu * Executing a command: umtool command_name * Get help of a command: umtool help command_name * Show this help: umtool /? or umtool -help It also works for subcommands: C:\WINDOWS\system32>umtool agtg --help Include an existing group into a group. Usage: umtool addgrouptogroup | agtg <group_to_add> <group_name> Examples: umtool addgrouptogroup testers developers I'm sorry I think it can't be changed. I'll double check just in case. it's not possible to have two Plastic SCM users with the same name. BTW, I checked your company has Enterprise support so please feel free to contact us at support at codicesoftware dot com in the future.
  15. Hi @Ramz-UK! the fix is now out :) Bug Plastic for windows: The option "Filter only parents" in the Version tree 2D was not correctly saved/restored. Now it's fixed. Further details here: https://www.plasticscm.com/download/releasenotes/8.0.16.2974
  16. Hi! Can you share how do you have it configured in the "client.conf" file (by default at "C:\Users\<your_user>\AppData\Local\plastic4")? My configuration that works fine is: <MergeToolData> <FileExtensions>.scene</FileExtensions> <Tools> <string>"C:\Program Files\Unity\Editor\Data\Tools\UnityYAMLMerge.exe" merge -p "@basefile" "@sourcefile" "@destinationfile" "@output"</string> </Tools> </MergeToolData> <MergeToolData> <FileExtensions>.prefab</FileExtensions> <Tools> <string>"C:\Program Files\Unity\Editor\Data\Tools\UnityYAMLMerge.exe" merge -p "@basefile" "@sourcefile" "@destinationfile" "@output"</string> </Tools> </MergeToolData> Best, Manu.
  17. I'm afraid we didn't do something to improve it But we are going to add a help card to allow you to resume the merge. Something like you see at the screenshot saying "You have a merge ready to checkin" but customized to help you to finish the merge.
  18. Hi @Earthchrome, yes, you have to go to the branch explorer or the changesets view and re-launch the merge to finish it. The error message will tell you the changeset number you need to merge from:
  19. Hi Chris! here you can learn how to enable the Plastic SCM plugin for Unity log: Please share with us the log generated and we will try to understand where the problem is. BTW, do you see extra information about the issue at the Window -> General -> Console panel? Best, Manu.
  20. Sorry for the long delay! @omris Revealed the unanswered topic.
  21. Hi @wayneh the Plastic SCM Step by Step tutorial will guide you through the creation of a new repository and a new workspace, it also explains how to import already existing content from git: https://www.plasticscm.com/documentation/labs/main If you don't want to import the code from git and you just want to add existing code to an empty repo you will need to copy or move the existing source code to the workspace path location. Then use the "add" operation to start tracking them and finally the checkin operation to confirm the changes. This guide perfectly illustrates what I'm explaining: https://www.plasticscm.com/branch-per-task-guide/gui/add-code-under-source-control Hope it helps!
×
×
  • Create New...