4 messages in com.perforce.perforce-user[p4] Problems with triggers
FromSent OnAttachments
John Griffin20 Nov 2000 10:55 
Jeff A. Bowles20 Nov 2000 12:03 
Yariv Sheizaf20 Nov 2000 22:11 
John Griffin21 Nov 2000 08:01 
Subject:[p4] Problems with triggers
From:Yariv Sheizaf (yar@cimatron.co.il)
Date:11/20/2000 10:11:54 PM
List:com.perforce.perforce-user

John,

For your second question :

You can find an example to pre-submit trugger on NT which send mail in :

public.perforce.com (public depot) in //guest/yael_stern/triggers/p4trig.pl .

For more help, call Miss Yael Stern : yaels at cimatron.co.il

Yariv

-----Original Message----- From: John Griffin [mailto:JohnG at sedonanetworks.com] Sent: Monday, November 20, 2000 8:56 PM To: 'support at perforce.com' Cc: 'perforce-user at perforce.com' Subject: [p4] Problems with triggers

Hello all, I am having difficulty with a Perforce pre-submit trigger. I am trying to send email, via a Perl script, whenever a update is done on a branch. The script works just fine from the command line. The script executes correctly as a pre-submit trigger on a box I have set up for test purposes. However, when I execute the Perl script as a Perforce pre-submit trigger on my production box it fails, though it does work from the command line. First question, is there any way to find out from Perforce why the script failed since all that I get on the command line is:

p4 submit -c 3079

Submitting change 3079. Submit validation failed -- fix problems then use 'p4 submit -c 3079'. Submit check 'notify_johng_1' failed: no error message

Second question, does anyone know of any NT issues related with sending emails within a Perforce pre-submit trigger?