You can specify complete paths or patterns. Then, configure the paths that will be exclusive checkouts.port is the port where the lock server is configured.server is the ip or the name of the lock server.If you want to specify rules for all repositories, the repname will be *. repname is the name of the repository where you want to perform exclusive checkouts on that particular repository.Create or edit the nf file on the server's directory with the following format:.Or Delete the rules for a repository if they aren't needed.

Repeat the steps above as many repositories need lock rules.Specify your own rules or load the suggested common lock rules by clicking 'Generate common rules' (you can edit them as well).Enter the name of the repository where the rules will apply.Click 'Add' in the 'Repository-specific rules' section.If you want to specify rules for a particular repository, then follow these steps:.If you want to configure global lock rules for all the repositories, in the 'Global rules (all repositories)' section you must specify the rules or load the suggested common lock rules by clicking 'Generate common rules'.To manage your locking rules from the Plastic SCM Server Administration Console: How can I configure a lock/exclusive setup?Įxclusive checkout, or locking a file, is useful in many scenarios where it's impossible to merge changes, like with:Ĭonfiguring exclusive checkout is as simple as adding or editing locking rules to the required repositories by managing your locking rules from the Plastic SCM Server Administration Console or by using a nf file.

Unity cloud build with plastic scm