Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Héber last won the day on July 17

Héber had the most liked content!

Community Reputation

1 Neutral

About Héber

  • Rank
    Advanced Member
  • Birthday March 14

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. Hi Wolfram, We have reproduced it and are going to keep it tracked. Thank you for the feedback. Best, Héber.
  3. 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.
  4. 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 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.
  5. Hi Pekka, 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. 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.
  6. Hi, I'm afraid there is no way to change the active workspace using the CLI. However, it is stored in the client.conf, so you could edit that file to switch it. You could probably have a script that changes it to a default one you are not going to delete. Does this make sense? Best, Héber.
  7. 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.
  8. 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.
  9. Hi Donald, If you are going to have a workspace there, you could have a trigger that runs an update each time a new changeset is merged or created in the branch, so it always has the latest content from the server. Here you have more info about triggers: https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide Best, Héber.
  10. 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.
  11. Hi, We are handling this via e-mail. We will update this thread once we have the solution. Best, Héber.
  12. Hi Matt, Yes, it is free. Don't worry about that message as it is a visual issue only. Once those days have ended, you will be able to keep working without any problems. Best, Héber.
  13. Héber

    Personal License

    Hi, Once you have your cloud organization up and running you can just create a new sync view for the repo you want to move to a new repo on the cloud server and run it. That would get you an exact copy of your local repo up there and you will be able to use it without issues. Then you have two options. Either you work distributed pushing your changes to the cloud, or you work centralized with the workspace pointing directly to the cloud server. I think it's easier the second one, but depending on your connection it might take you some time. You could also work only locally. Best, Héber.
  14. Hi Jeff, I'm sorry for the late reply. As you said, we don't encourage the modification of the history because it can lead to this kind of scenarios. The only way to fix it without having to create a new local repo is to have another teammate create a new changeset where the deleted one was supposed to be, as you did. I'm sorry for the inconvenience. Best, Héber.
  15. Hi, I'm afraid there is no way to do it right now. We are working on a trimming tool to reduce the space that it takes, bt right now it is not possible. Another option I can think of, if you don't need all the branches for example, you could replicate to a new repo only the main branch and the ones you are currently using and then delete the previous repo. This is not an optimal option, but it might help you save some space. I'm sorry for the inconvenience. Best, Héber.
  • Create New...