p4 jobs

Synopsis

List jobs known to the Perforce server

Syntax

Description

When called without any arguments, p4 jobs will list all jobs stored on the server. Its various flags and arguments can be used to limit the listing to a subset of the known jobs. The jobs listed can be limited to those that are linked to changelists that affected particular files, or to those jobs that contain certain words.

Jobs are listed in 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 file ... The files or file patterns provided may contain revision specifiers or a revision range.

Options

Usage Notes

Job Views

Use p4 jobs -e jobview to limit the list of jobs to those that contain particular words. You can specify that the search terms be matched only in particular fields, or anywhere in the text of the job. You can use jobviews to match jobs by values in date fields, though there are fewer options for dates then there are for straight text.

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's. 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'. 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 are available. They are:

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.

Other Usage Notes

• The p4 user form has a JobView: field that allows a jobview to be linked to a particular user. After a user enters a jobview into this field, any changelists he creates will automatically list jobs that match the jobview in this field. The jobs that are fixed by the changelist can be left in the form, and the jobs that aren't should be deleted.
• p4 jobs orders its list output alphanumerically order by job name. If you use job names other then the standard Perforce names, this order won't help much.
• The -m max flag displays the first max jobs in alphanumeric order, not the max latest jobs.

Limitations

• Jobviews cannot be used to search for jobs containing null-valued fields. In other words, if a field has been deleted from an existing job, then the field is not indexed, and there is no jobview that will match this `deleted field' value.
• The jobview not operator '^' can be used only after an and within the jobview. Thus, the jobviews 'gui ^name=joe' and 'gui&^name=joe' are valid, while the jobviews 'gui|^name=joe' and '^name=joe' are not.

'Examples

Related Commands