Re: [p4] Using change-failed trigger

We recently started using %maxErrorSeverity% and %maxErrorText%, although not in the change-failed trigger.
The former contains just one word - like error, warning, or 'empty' (not the change-failed case though).
The %maxErrorText% is the error message, and that's what you would have to use to determine the cause of the failure.

--
Michael Mirman
MathWorks, Inc.
3 Apple Hill Drive, Natick, MA 01760
508-647-7555

> -----Original Message-----
> From: perforce-user [mailto:[email protected]] On Behalf
> Of Sambwise
> Sent: Tuesday, February 20, 2018 12:25 PM
> To: [email protected]
> Subject: Re: [p4] Using change-failed trigger
> 
> Posted on behalf of forum user 'Sambwise'.
> 
> I haven't ever used a change-failed trigger, but scanning over the list of
> args in "p4 help triggers" this looks like the most likely thing:
> 
> %maxErrorSeverity% -- highest error seen for this cmd %maxErrorText% -- text
> and
> errno for highest error
> The error codes will map to the Error object in the C++ API; you can also view
> these for a command line error with the "-e" global flag.
> 
> 
> 
> --
> Please click here to see the post in its original format:
>   https://protect-
> us.mimecast.com/s/H508CPNGpPFJERXizDaZe?domain=forums.perforce.com
> _______________________________________________
> perforce-user mailing list  -  [email protected]
> https://protect-
> us.mimecast.com/s/ZvHqCQWXqQfJjpPiP27TW?domain=maillist.perforce.com

_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user