christopher.hahn at peregrine.com
Thu Oct 25 21:48:01 PDT 2001
You "order of trigger rules" comment is excellent,
but the trigger name is only used once.
I am going to confirm that the script is really
running, as suggested by another user.
Thank you for the time,
P.S. The current form that I am testing is:
# Grab params
$clistnum = shift;
$port = shift or $port = "perforce-sd:1666";
print STDOUT "This test message should appear when the submission fails";
print STDOUT "The arguments to this script were $clistnum and $port";
From: Mike Castle [mailto:mcastle at yy.com]
Sent: Thursday, October 25, 2001 6:26 PM
To: Perforce-User (E-mail)
Subject: Re: [p4] Triggers
On Thu, Oct 25, 2001 at 05:32:55PM -0700, Christopher Hahn wrote:
> I could swear that I have seen this done, but it
> does not appear that either the triggers stdout
> nor it's stderr are grabbed by perforce, for display.
Are you sure your script is being ran? Put a date > /tmp/foo or something
like that in the script to verify it's being ran.
Then do a simple one like:
fail.cmd (for win32)
One thing I had to remember to do was to make sure that different types of
triggers have different names.
If I have something like
foo //tree/branch/... "my.cmd %client%"
foo //tree/branch2/... "my2.cmd %client%"
That my.cmd was going to be ran in both cases. Are you sure that's not
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user