I understand that a lable is applied by build manager on different versions of files to mark a baseline. I would like to prevent developers moving this label to the different version of the same file. Would like to know the different ways to manage this in PVCS Version Manager.

Also would like to check for the comment field for specific key words at the time of check in and allow the check in only if the words match my criteria. I understand this can be done using triggers and would like to know more details.

Appreciate any info on the above 2 queries.

Regarding the labels you will want to look at the Privileges under User/Project Security. In particular the Add, Modify and Delete Version Label privileges.

Regarding the trigger check out the Using Event Triggers chapter of the Administrators Guide. This has the info to set them up and gives a short example. I am not sure how to stop the check in process with a trigger however. I think you have your script return a non-zero exit code, but I'm not sure.

Thanks John for the pointer.

Hi Thr,

Stop checkin, if comment is not as required. Is possible, if you are using unix machine and using command line commands....

rgds,
KVK

Hi,

I have written a trigger for the same in wscript, if u need i can send it to u.

Hello,

I'm returning to VM after 8 years and interested in locking labels and forcing labels to be applied on check-in. If you have a script, please send it to me. Thanks a bunch in advance.


-Smitty

This ensures a label is applied (a wscript file):

Set objShell = WScript.CreateObject("WScript.Shell"
if objShell.Environment("PROCESS".Item("EVENTVERSION"="" then
objShell.Popup "Version Label Must Be Specified!",0,"PVCS Version Manager",0
Wscript.quit(-1)
end if

To check the labels (e.g. making sure this has not been applied before on the repository) takes a lot more work.

Regards Neil.