Determining the last changelist synced to in Perforce

I recommend the opposite for automatic build systems: you should first get the latest changelist from the server using:

p4 changes -s submitted -m1

then sync to that change and record it in the revision info. The reason is as follows. Although Perforce recommends the following to determine the changelist to which the workspace is synced:

p4 changes -m1 @clientname

they note a few gotchas:

• This only works if you have not submitted anything from the workspace in question.
• It is also possible that a client workspace is not synced to any specific changelist.

and there's an additional gotcha they don't mention:

• If the highest changelist to which the sync occured strictly deleted files from the workspace, the next-highest changelist will be reported (unless it, too, strictly deleted files).

If you must sync first and record later, Perforce recommends running the following command to determine if you've been bit by the above gotchas; it should indicate nothing was synced or removed:

p4 sync -n @changelist_number

Just to answer this myself in keeping with Jeff's suggestion of using Stackoverflow as a place to keep technical snippets....

From the command line use:

p4 changes -m1 @<clientname>

And just replace with the name of your client spec. This will produce output of the form:

Change 12345 on 2008/08/21 by joebloggs@mainline-client '....top line of description...'

Which is easily parsed to extract the changelist number.