Fog Creek Software
Discussion Board

Perforce, Passwords, etc.

Apparently if you have passwords enabled on your perforce server, the only way to get the trigger script to work is to either remove the -u $Username from the p4 command or to hardcode a password value.

This is because the triggers can't pass passwords to the trigger script, so the trigger script can't run p4 as the user that is submitting the source change.

Does anyone that is familiar with Perforce know of any way around this?

Michael H. Pryor
Fog Creek Software
Thursday, June 17, 2004

I don't believe there is -- since there's no way to get the password from the changelist description (which I think is a GOOD thing). I think the solution is as I laid out in the thread linked to above -- create a user that has "list" access to the entire depot and have that user enter the bug information.

I do have a support request into Perforce about a similar issue with perfbrowse and will post whatever they tell me.

Corey Reid
Tuesday, June 29, 2004

*  Recent Topics

*  Fog Creek Home