Jump to content

ollieblanks

Administrators
  • Posts

    268
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by ollieblanks

  1. Hi,

    • The Repo URL field should be in the format "CloudOrgName@cloud". Once you get past this step and you set up Build Targets in Cloud Build you will select which repository and branch that you will build from.
    • The Username field should be the email address associated with your Plastic SCM account.
    • The Password field should be your password associated with your Plastic SCM account.
    • The Authentication Type should be set to LDAP.
    • The Encryption Key is the client-side passphrase you configured when you first set up encryption. If you cannot remember this passphrase, you should be able to use the crypted content within your User/AppData/Local/Plastic4/***.key file
    • The Encryption Method should be set to AES128.

    Hope this helps!

  2. Hi @AndyDB

    It's important to note that Unity Organizations and Plastic SCM Organizations are separate entities at this time. This means that just because you have been granted access to the Project via the Unity side this doesn't mean you are granted access via Plastic SCM.

    I see you have logged a support ticket, so I will continue to assist you there and circle back once we resolve it!

  3. I guess the size of your repository is what is causing your disk space to be used up. If you are using a distributed workflow, a centralised workflow may be better, because you only need to have a workspace pointing at your repository server and you do not need to have the entire repository replicated on your machine.

    Also, if you wish to pull only part of the repository, then Gluon may be a better UI for you.

    Hope this helps.

  4. Hi,
    Thank you for reaching out with this interesting scenario.

    Unfortunately, there is no way to transfer the lock of a file to another user, without that user's interaction.

    My suggestion would be to allow the interns to check in changes only to a specific branch on the project repository and once it has been reviewed it is then merged into a main branch that the developers also work on. This could in theory be very similar to following the branch-per-task workflow. This way, if a developer needs access to an early "un-reviewed" version of a model, then they could just merge from the artist's task-branch.

    Additionally, this would allow you to utilise the Code Review system for the Senior artist review process, which could also be tracked by the developers, giving higher level of visibility of the progress on a specific model.

    I hope I have understood your requirement here. Please let me know if this does not fit your need, and I will be happy to assist further.

  5. I believe this may have been caused by an outage on March 30th. If you are still experiencing this behaviour, please check if this issue occurs in the Plastic SCM client, double check your internet connection and any 3rd party software that may be affecting your access and if you are still having issues, please log a support ticket with us.

    Hope this helps.

×
×
  • Create New...