| Perforce 99.2 Command Reference (99.2.cr.3) | ||
|
<< Previous Chapter p4 job |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 jobspec |
Jobs are listed in alphanumeric order (or, if you use the -r flag, in reverse alphanumeric order) by name, one job per line. The format of each line is:
jobname on date by user *status* description
The description is limited to the first 30 characters, unless the -l (long) flag is used.
If any of the date, user, status, or description fields have been removed by the Perforce superuser with p4 jobspec, the corresponding value will be missing from each job's output.
To limit the list of jobs to those that have been fixed by changelists that affected particular files, use p4 jobs filespec The files or file patterns provided may contain revision specifiers or a revision range.
|
-e jobview |
List only those jobs that match the criteria specified by jobview. Please see the Usage Notes below for a discussion of job views. |
|
-i files ... |
Include jobs fixed by changelists that affect files integrated into the named files. |
|
-l |
Output the full description of each job |
|
-m max |
Include only the first max jobs, sorted alphanumerically. If used with the -r flag, the last max jobs are included. |
|
-r |
Display jobs in reverse alphabetical order by job name. |
|
-R |
Rebuild the job table and reindex each job. Reindexing the table is necessary only when upgrading from version 98.2 or earlier to version 98.3 or higher and only needs to be performed once. |
|
See the Global Options section. |
Text matching is case-insensitive. Each word is treated individually; phrases are not matched. Use alphanumeric text only, with no punctuation. You cannot use wildcards in jobviews.
The jobview `word1 word2 ... wordN' can be used to find jobs that contain all of word1 through wordN in any of the job's fields. Spaces between search terms in jobviews act as boolean AND operations. To find jobs that contain any of the terms, separate the terms with the "|" character. Ampersands (&) can be used as boolean ANDs as well; the boolean operators bind in the order &, |, space (highest precedence to lowest precedence). Use parentheses to change the grouping order.
Search results can be narrowed by matching values within specific fields with the jobview syntax"fieldname=value". The value must be a single alphanumeric word.
Date fields can be matched by expressing the jobview date as yyyy/mm/dd or yyyy/mm/dd:hh:mm:ss. If a specific time is not provided, the equality operator (=) matches the entire day.
The usual comparison operators (=, >, <, >=, and <=) are available.
Additionally, you can use the NOT operator (^) to negate the sense of some comparisons. (See Limitations, below, for details).
The behavior of these operators depends on the type of job field you're comparing against:
If you're not sure of a field's type, run p4 jobspec -o, which outputs the job specification used at your site. The p4 jobspec field called Fields: contains the job fields' names and datatypes. See p4 jobspec for a discussion of the different field types.
|
To create or edit an existing job | |
|
To attach a job to a particular changelist, indicating that the job is fixed by that changelist | |
|
To list all jobs and changelists that have been linked together | |
|
To view all the information about a particular changelist, including the jobs linked to the changelist | |
|
To change the format of the jobs used on your server (superuser only) | |
|
To read information about the format of jobs used on your site (any user) |
p4 jobspec -o |
|
To set a default jobview that will include jobs matching the jobview in all new changelists |
| Perforce 99.2 Command Reference (99.2.cr.3) | ||
|
<< Previous Chapter p4 job |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 jobspec |