Jump to content

manu

Administrators
  • Posts

    4,599
  • Joined

  • Last visited

  • Days Won

    130

manu last won the day on September 27 2021

manu had the most liked content!

1 Follower

About manu

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

41,429 profile views

manu's Achievements

  1. Hello, I'm not sure which administrator to go to for this, but the Plastic SCM servers in AsiaEast are down. I can confirm that other teams throughout this region are having the same problem. I attached a picture of the error message that we are receiving. Is there anyway we could get some information or updates on this situation? This has essentially halted the workflow for my entire team, and I imagine its the same for other teams throughout this region. 

    Thanks,

    Trevor

    server error.PNG

  2. Hi @DaSHTech! That's an idea that has been flying around a dew times in the past. We initially discarded it because the diff view takes a lot of space, making the view very messy. Are you referring to only the list of changed files but not the diff op, or also the diff op?
  3. 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
  4. 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.
  5. 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.
  6. 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.
  7. 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
  8. 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:'/')
  9. 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.
  10. 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,
  11. 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?
  12. 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.
  13. 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.
×
×
  • Create New...