I have a file that is locked/checked out exclusively by a user who is no longer with the company. I need to make changes and want to know how to "steal the lock".
To unlock those files: p4 [g-opts] unlock [-c change | -s shelvedchange | -x] [-f] [file ...] This releases locks that were created explicitly using the p4 lock command, or implicitly during the course of a submit operation.
Right-click on the file. In the menu that appears, select Lock File. To unlock, right-click the file and select Unlock File.
By default, Perforce does not do an exclusive check out, which means that other members of your team may be working on the same files at the same time. Communication is key to avoid merge conflicts that can be time-consuming and difficult to resolve.
To unlock those files on the commit server, either the user who issued the failing command unlocks them: specifying the name of the workspace the files are locked in as the -c global flag to p4. DVCS: Files might be locked on a remote sever from a failed p4 push.
specifying the name of the workspace the files are locked in as the -c global flag to p4. If p4 unlock is called from an Edge Server, any corresponding files locked globally via p4 lock -g by that client will be unlocked on the Commit Server. Unlock files in pending changelist changelist.
specifying the name of the workspace the files are locked in as the -c global flag to p4. DVCS: Files might be locked on a remote sever from a failed p4 push. To unlock those files on the remote server, either the user who issued the failed push command unlocks them:
As Peter G. said, an admin can unlock a file with the unlock command: p4 unlock -f <file> However, to revert a file checked out by another user, you need to impersonate that user by passing their client (workspace name), host (computer name) and user names to the revert command, like so: p4 -c theirclient -H theirhost -u theiruser revert filename
Ask your perforce admin to remove the lock by issuing
p4 unlock -f <file>
PS: To reuse the departed user's license, your perforce admin might also want clean up the files left opened by him. He can revert the pending edits if they are useless or transfer them to another user via "p4 reopen".
The "reopen" and "revert after reopen" can also be performed by ordinary users.
"Locked" and "checked out" are two different things which require two different operations to undo. As Peter G. said, an admin can unlock a file with the unlock command:
p4 unlock -f <file>
However, to revert a file checked out by another user, you need to impersonate that user by passing their client (workspace name), host (computer name) and user names to the revert command, like so:
p4 -c theirclient -H theirhost -u theiruser revert filename
So if a Perforce user named jdoe has file foo.txt checked out in workspace ws1 on a host named joesPC, an admin can revert it with the following command:
p4 -c ws1 -H joesPC -u jdoe revert foo.txt
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With