Upgrade & Secure Your Future with DevOps, SRE, DevSecOps, MLOps!
We spend hours scrolling social media and waste money on things we forget, but won’t spend 30 minutes a day earning certifications that can change our lives.
Master in DevOps, SRE, DevSecOps & MLOps by DevOpsSchool!
Learn from Guru Rajesh Kumar and double your salary in just one year.
Get Started Now!
Use the following variables in the command field to pass data to a trigger script:
|
|
|
|
|
|
Either null or a string reflecting an action taken to a changelist or job. For example, “pending change 123 added” or “submitted change 124 deleted” are possible %action% values on change forms, and “job000123 created” or “job000123 edited” are possible %action% values for job forms. |
|
|
|
The number of the changelist being submitted. The abbreviated form %change% is equivalent to %changelist%. A change-submit trigger is passed the pending changelist number; a change-commit trigger receives the committed changelist number. |
change-submit,
change-content,
change-commit,
fix-add,
fix-delete,
form-commit,
shelve-commit |
|
|
The root path of files submitted |
|
|
|
Triggering user’s client workspace name. |
|
|
|
|
|
|
|
The IP address of the client. |
|
|
|
A string of job numbers, expanded to one argument for each job number specified on a p4 fix command or for each job number added to (or removed from) the Jobs: field in a p4 submit, or p4 change form. |
|
|
|
If a changelist is renumbered on submit, this variable contains the old changelist number. |
|
|
|
Hostname of the Perforce server. |
|
|
|
The IP address of the server. |
|
|
|
The IP address and port of the Perforce server, in the format ip_address:port. |
|
|
|
The P4ROOT directory of the Perforce server. |
|
|
|
Perforce username of the triggering user. |
|
|
|
Path to temporary form specification file. To modify the form from an in or out trigger, overwrite this file. The file is read-only for triggers of type saveand delete. |
form-commit,
form-save,
form-out,
form-in,
form-delete |
|
|
Name of form (for instance, a branch name or a changelist number). |
form-commit,
form-save,
form-out,
form-delete |
|
|
Type of form (for instance, branch, change, and so on). |
form-commit,
form-save,
form-out,
form-in,
form-delete |
|
|
Operation: read, write, or delete |
|
|
|
Path of archive file based on depot’s Map: field. If the Map: field is relative to P4ROOT, the %file% is a server-side path relative to P4ROOT. If the Map: field is an absolute path, the %file% is an absolute server-side path. |
|
|
|
|
|
Certification Courses
DevOpsSchool has introduced a series of professional certification courses designed to enhance your skills and expertise in cutting-edge technologies and methodologies. Whether you are aiming to excel in development, security, or operations, these certifications provide a comprehensive learning experience. Explore the following programs:
Explore our DevOps Certification, SRE Certification, and DevSecOps Certification programs at DevOpsSchool. Gain the expertise needed to excel in your career with hands-on training and globally recognized certifications.
