bcrickcwru Posted June 27, 2016 Report Share Posted June 27, 2016 Hi! I'm new to PlasticSCM and am setting up a new repository on the cloud service. I'm a developer using the PlasticSCM client proper, which is working fine... but when I set up Gluon for our artist, I'm getting weird errors. Several hundred files appear to be locked and checked out to the artist. The Check In option isn't available. And when we try Check Out, there's an error message saying "These items are exclusively checked out by [artist name]." Is there anyway to reset the checkouts on these files? Thanks, Brian Link to comment Share on other sites More sharing options...
manu Posted June 29, 2016 Report Share Posted June 29, 2016 Hi Brian, yes, first you need to be the repository server owner. Open a regular Plastic SCM client, repositories, right click in any of them and select "Repository server permissions" then change the owner to yourself. Now from the command line you can use the "cm unlock" command in order to remove the pending locks. Obviously there's an easier way to do it, from the machine having the locks open the Plastic SCM GUI and undo them all. The lock will be released. Link to comment Share on other sites More sharing options...
applenaut Posted July 12, 2018 Report Share Posted July 12, 2018 Is there a way to unlock all files with a single command? Link to comment Share on other sites More sharing options...
calbzam Posted July 13, 2018 Report Share Posted July 13, 2018 Hi Brian, No sorry, you will need to release the locks one by one with "cm unlock". Regards, Carlos. Link to comment Share on other sites More sharing options...
FLARB Posted October 6, 2020 Report Share Posted October 6, 2020 I have this same problem--2 years later and you still have to unlock every individual file by hand? This is quite literally the worst source control product I've ever used. Link to comment Share on other sites More sharing options...
psantosl Posted October 6, 2020 Report Share Posted October 6, 2020 Hi, Please understand this is not the regular workflow. The way to abandon locks is: You checkout 100 files (probably not a common thing to do, anyway). Then you delete your workspace. Then your locks are lost. I would say, based on all our other customers, that abandoning a workspace with locks in it is not a common thing to do. Of course it can happen, and yes, of course we can have a better interface for handling that, but we consider this a rather corner case, otherwise we'd be running into it every single day, and fortunately we do not. Quote This is quite literally the worst source control product I've ever used. We are here to try to make our customers happy. If you really think Plastic is the worse version control you ever used, then my recommendation is: "please stop using it". I prefer that you are happy using a competitor than unhappy using us. Link to comment Share on other sites More sharing options...
Settius Posted November 12, 2021 Report Share Posted November 12, 2021 Is there any way to unlock multiple (over 100, even 1000) files for specific user, workspace or any other query? Link to comment Share on other sites More sharing options...
calbzam Posted November 12, 2021 Report Share Posted November 12, 2021 Hi, If you are using an on-premises server, you may need to manually edit the locked items on the server side. If you are using Plastic Cloud edition, I'm afraid you will need to manually run the "cm unlock" commands. But If the user still has the items locked in their workspace, they can use "cm unco --help" to undo checkout on the items and this way release the locks ("Undo Changes" if you are using the Plastic GUI). Regards, Carlos. Link to comment Share on other sites More sharing options...
Settius Posted November 12, 2021 Report Share Posted November 12, 2021 Why is the "cm unlock" so limited? Link to comment Share on other sites More sharing options...
calbzam Posted November 15, 2021 Report Share Posted November 15, 2021 - I agree that it's not very comfortable if you need to unlock tons of items via this command? But why do you need it? it's not very common. As a normal basis, undoiing the changes in the workspace will release the locks. - I'm guessing if you could pipe the guid value from the outpout of "cm listlocks --help" to the "cm unlock --help". Regards, Carlos. Link to comment Share on other sites More sharing options...
lrg_steven Posted November 17, 2021 Report Share Posted November 17, 2021 We are having an issue on Cloud where a file is locked, the user who locked the file has nothing in their pending changes, the user can not "Undo Checkout", the repository owner on Plastic SCM can not "Undo Checkout", and "cm unlock" on the repository owner's machine does not unlock the file. Link to comment Share on other sites More sharing options...
lrg_steven Posted November 17, 2021 Report Share Posted November 17, 2021 Since cm unlock doesn't have any output, we didn't realize that the command wanted a GUID Link to comment Share on other sites More sharing options...
lrg_steven Posted November 17, 2021 Report Share Posted November 17, 2021 Is there an easy way to get the GUID from the Plastic SCM GUI? Link to comment Share on other sites More sharing options...
calbzam Posted November 17, 2021 Report Share Posted November 17, 2021 Hi, I'm afraid you will need the CLI to release the locks and get the guids: cm listlocks --help cm unlock --help Regards, Carlos. Link to comment Share on other sites More sharing options...
lrg_steven Posted November 17, 2021 Report Share Posted November 17, 2021 Thanks for the info! Any idea what could cause a file to become locked without having it in Pending? Link to comment Share on other sites More sharing options...
calbzam Posted November 17, 2021 Report Share Posted November 17, 2021 Hi, Normally it happens when you remove a workspace (or re-create it) without previuously relasing the pending locks. Regards, Carlos. Link to comment Share on other sites More sharing options...
NilloPillo Posted August 3, 2022 Report Share Posted August 3, 2022 Hey, Ran into this issue as well because I deleted the repo while having a bunch of files locked out. I managed to automate the unlocking process for hundreds of files with a batch script. First use "cm listlocks > out.txt" to save the output to a txt file. Open the txt file (I was using Rider to do this) and delete everything except for the hashes. on each line add cm lock unlock at the start of the line (so you end up with something like this: cm lock unlock 7525e94c-2722-41b9-953f-a4011cffc932 cm lock unlock aa8e7596-0a5c-4242-b743-279dac99ab9e cm lock unlock c60a72a1-80dc-4522-bf15-6fa40a0aeda7 cm lock unlock 4577883f-c479-4359-988e-82ca40fcf798 cm lock unlock f20db7f1-01cf-4dc9-8e9c-30ea944d2a2b Save that file as "unlock.bat" or whatever name with the .bat extension. Open a cmd in the repo directory and press tab until you get the .bat file you just made, hit enter and watch it unlock all your files (albeit very slowly, it will do it automatically). Hope that helps anyone out there in lock hell! -Nils Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now