p4 jobspec
Synopsis
Edit the jobs template.
Syntax
p4 [g-opts
] jobspec
p4 [g-opts
] jobspec
[-i]
p4 [g-opts
] jobspec -o
Description
The p4 jobspec
command presents the Perforce administrator with
a form in which job fields can be edited, created, deleted, and refined.
Do not confuse the names of the fields in the p4 jobspec
form
with the names of the fields within a job. The fields in the p4
jobspec
form are used to store information about the fields in the
p4 jobs
form.
Form Fields
Field Name | Description |
---|---|
|
A list of field definitions for your site’s jobs, one field per line. Each line is of the form code name datatype length fieldtype.
|
|
Contains a lists of fields and valid values for Enter one line for each field of datatype
|
|
Contains a list of fields and their default values for each field that
has a fieldtype of Each line must contain the field name and the default value, separated by a space. For example:
Any one-line string can be used, or one of three built-in variables:
See Usage Notes for special considerations for field 102. |
|
Textual comments that appear at the top of each See Usage Notes for special considerations for these comments if your users need to enter jobs through P4V, the Perforce Visual Client. |
Options
|
Read the jobspec form from standard input. |
|
Write the jobspec form to standard output. |
|
See “Global Options”. |
Usage Notes
Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
---|---|---|
N/A |
N/A |
|
-
Do not attempt to change, rename, or redefine fields 101 through 105. These fields are used by Perforce and should not be deleted or changed. Only use
p4 jobspec
to add new fields (106 and above) to your jobs.Field 101 is required by Perforce and cannot be renamed nor deleted.
Fields 102 through 105 are reserved for use by Perforce applications. Although it is possible to rename or delete these fields, it is highly undesirable to do so. Perforce applications may continue to set the value of field 102 (the
Status:
field) toclosed
(or some other value defined in thePresets:
for field 102) upon changelist submission, even if the administrator has redefined field 102 to for use as a field that does not containclosed
as a permissible value, leading to unpredictable and confusing results. - The information in the
Comments:
fields is the only information available to your users to tell them how to fill in the job form, and is also used by P4V, the Perforce Visual Client, to display tooltips. Please make your comments complete and understandable. -
The
Presets:
entry for the job status field (field 102) has a special syntax for providing a default fix status forp4 fix
,p4 change
-s, andp4 submit
-s.By default, a job’s status is set to closed after you use
p4 fix
,p4 change
, orp4 submit
. To change the default fix status fromclosed
to some otherfixStatus
(assuming that you have defined thefixStatus
as a validselect
setting in theValues:
field), use the special syntax of
in thejobStatus
,fix/fixStatus
Presets:
field for field 102 (job status). To change the behavior ofp4 fix
,p4 change
, andp4 submit
to leave job status unchanged, use the specialfixStatus
ofsame
. - See the "Customizing Perforce: Job Specifications" chapter of the Helix Versioning Engine Administrator Guide: Fundamentals for an example of a customized jobspec.