#
# Copyright 2005 Perforce Software. All rights reserved.
#
# Perforce Submit and Form Validating Trigger Specifications.
#
# Triggers: a list of triggers; one per line. Each line has four
# elements:
#
# Name: The name of the trigger.
#
# Type: 'submit' for pre-submit triggers. 'content' for
# mid-submit triggers with access to file content.
# 'commit' for post-submit triggers. 'in', 'out',
# 'save' or 'delete' for form triggers.
#
# Path: For submit triggers, a file pattern to match files
# in the changelist. For form triggers, the type of
# form ('branch', 'client', etc).
#
# Command: The OS command to run for validation. If the
# command contains spaces, the whole command must
# be quoted. See 'p4 help triggers' for a list of
# variables that can be expanded in the command
# string.
#
# For example,
#
# Triggers:
# example submit //depot/... "runcommand %changelist%"
#
# See 'p4 help triggers' for more information about triggers.
Triggers:
ejsjobin in job "RUBY_BIN -I TRIGGERS_DIR TRIGGERS_DIR/job_in.rb %user% %formfile%"
ejsjobdel delete job "RUBY_BIN -I TRIGGERS_DIR TRIGGERS_DIR/job_delete.rb %user% %formfile%"
ejsjobcommit form-commit job "RUBY_BIN -I TRIGGERS_DIR TRIGGERS_DIR/job_commit.rb %user% %formfile% %quote%%action%%quote%"
ejsspecsave save spec "RUBY_BIN -I TRIGGERS_DIR TRIGGERS_DIR/spec_save.rb %user% %formfile% %formname% %formtype%"