Jump to content

Héber

Administrators
  • Posts

    175
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by Héber

  1. Hi,

    You need to set up a cloud organization and install PlasticSCM cloud edition. With each cloud edition installation, a local server is installed, so when it asks you to create a new repo you have to create it under the "local" server. 

    The "work distributed" section of the guide is what you want, without pushing the changes and keeping in mind that the name of the server is just "local", not "localhost:8087":

    https://www.plasticscm.com/documentation/cloud-edition/plastic-scm-version-control-cloud-edition-guide#WorkdistributedwithPlastic

     

    Best,

    Héber.

    • Like 1
  2. Hi,

     

    Yes, running this command would be enough to check-in all the hidden changes, but it wouldn't allow you to review them if needed:

    cm status --hiddenchanged --short --compact | cm co - && cm ci

    cm status --hiddenchanged --short --compact | cm co - && cm ci

    So, your script should work without issues. 

    What else are you missing in your script? Anything I can help you with?

     

    Best,

    Héber.

  3. Hi,

    First of all, I'm sorry for the late reply, I totally miss the thread.

    Regarding the request, I guess having those files not showing in the pending changes view until the moment you want to check them in is not an option, right? Because having your users select the option to show the hidden files in the pending changes view right before checking everything in could be a way to go:

    image.png

    I'm afraid using the CLI is not possible, as you would need to remove the files from the hidden changes list before checking them in, and then re-add them. 

    However, I'll share it with the team just in case.

     

    Best,

    Héber.

     

  4. Hi,

    We do have a workaround for these cases, check out this link:

    https://plasticscmsupport.zendesk.com/hc/en-us/articles/360013103159-How-to-Install-Plastic-GUI-in-Ubuntu-19-10-and-later-

    Regarding the fix, it is not a trivial matter as it relies on the mono-based libraries out there, but we are already exploring some alternatives to have a full multi-platform GUI that should avoid this issue.

    I'm sorry for the inconvenience.

     

    Best,

    Héber.

  5. Hi,

     

    Are you working against a cloud organziation?

    Can you check that the local server service is up and running? 

    Have you noticed any  issues in the network lately? 

    How big is the check-in?

     

    Furthermore, if you can contact us in "support@codicesoftware.com" and send us your client "plastic.debug.log.txt" files located in your local configuration folder, we could have a look at it.

     

    Best,

    Héber.

  6. Hi ,

    Are you using the Unity new plugin?

    Can you update it too? We had an issue that modified the existing ignore.conf to add the default rules we provide.

    Aside from that, how are you sharing the ignore.conf? Do you have it controlled in the repo or are you using the plastic-global-config repo to share it?

     

    Best,

    Héber.

  7. Hi Ofir,

    I'm afraid CentOS 8 has dropped compatibility with Gnome2, which we use for our interfaces and that is preventing you from downloading the graphical client. Maybe you could try to add the repos for CentOS7 and try to download the library there, but I'm not sure if it is going to be possible.

    You should be able to install the command line client and the server though, but you have to do it separately.

    I'm sorry for the inconvenience.

    Best,

    Héber.

     

  8. Hi,

    Locks work for the whole repo so far. So, if you lock a file in the main branch and then create a new branch with that file locked, the file is going to be lockked in that branch too. If now you release the lock, it is going to be released in the main branch too. Can you share why would you need to find which branch has a lock?

    For the performance question, you can run the "cm lock ls" for the current user or workspace, but I think that is not what you need?

    The rev specification is to add the id of the revision, so you can't use wildcards for a branch because it is not going to get a branch. It would be something like:

    cm lock ls rev:4321

    We have though of some improvements we want to add, but we haven't implemented them yet. You can have a look at a discussion about them here:

     

    Best,

    Héber.

     

  9. Hi Pekka,

    I'm afraid there is misconception here. It is not that Gluon allows you to work without a local database and Plastic doesn't. Both of them allow you to work that way, you just need to set it up so the workspaces are pointing directly against the server. Check out this guide:

    https://www.plasticscm.com/documentation/cloud-edition/plastic-scm-version-control-cloud-edition-guide#Workcentralized,distributedorboth

    Quote

    If I understood this correctly, this would require an on-premise server. I suppose it might work, but I don't think in our case there's will to start administering our own instance when people are not sold on the idea yet.

    Yes, you are understanding it correctly  but you can have an on-premise server with a cloud edition without allowing the rest of the users to access it. It would be a server in that machine only available for that machine. When that machine needs to get the content or share it with the rest, you would just need to push/pull to the cloud server.

     

    Best,

    Héber.

  10. Hi Pekka,

    I'm thinking how a Gluon-like version control could benefit them in their work.

    With Gluon you can download only the content you want from the server, so you could get only the files you are going to work within that day and thus save space in the local machine. I can link this to the question about purging space in the local machine. If you work in a centralized way, you will only have the content on the workspace in the machine, not the entire history. That added to using Gluon will allow your artists to save a lot of storage by just having what they need to work at the moment.

     

    A practical option could be just figuring out some command line magic to mirror a project to a network drive...

    I'm wondering if having a workspace pointing at that network drive, to the latest changeset, and using triggers will do the trick. You could have a trigger that after a checkin is made against the server, that workspace runs an update operation so it gets all the content it needs. Then, the files are rendered and checked-in to the central server again. Could this be an option?

    Regarding the folders, you would like to organize all the repos you have (especially the ones you no longer use I guess) into folders? I'll share that with the team. Just keep in mind that you can remove repositories from the server without actually needing to delete them. You can remove them from the list but the folder will still be in the Jet database and you could add it later in case you need it. You can have a look at the repositories under the source control and the folder they correspond to by running a " cm lrep --format=TABLE".

    Let me know what you think about this.

    Best,

    Héber.

  11. Hi Xavier,

    We are handling this issues trhough e-mail. We will update the thread once it is solved.

    Regarding the requests, the plugin is being improved right now and I think the "undo unchanged" button will be added soon. 

    Best,

    Héber.

  12. Hi Anton,

     

    When you check-out a file, you are telling Plastic that you are going to modify that file, so it doesn't have to go through the whole workspace looking for files that have changed. But I would say that the main reason is to work with locks, as you need to perform a checkout to get the lock of a file (if you have a rule configured). Here you can have a look at it:

    https://www.plasticscm.com/documentation/cli/plastic-scm-version-control-cli-guide#Changedvscheckedout

     

    Best,

    Héber.

  13. Hi,

    Once you start a project you might want to prevent some files from being uploaded to the server in any case. If you use an ignore.conf, all the ignored files won't appear to be added in the pending changes view. But it onnly works with private files, so, if anyone uploads a file to the server that you have ignored, and then you download that file, the next time you perform a check-in that file will be submitted because now it is ccontrolled.

    I'll leave you a blog post entry about the ignore.conf here:

    http://blog.plasticscm.com/2014/11/configuring-ignored-items-on-your.html

    Best,

    Héber.

×
×
  • Create New...