Detecting Perforce unopened modified files

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

I think your problem is likely to be with the mappings. This is a reasonably common issue.

Taking your details

Workspace root: C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666

File dir under root: C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel_files

View mappings:

//tunnel/... //wtansill_localhost_1666/tunnel/...

//tunnel/* //wtansill_localhost_1666/tunnel/*

With the details above, the line

//tunnel/... //wtansill_localhost_1666/tunnel/...

means that you need to place the files you wish to add into the root of your workspace plus the directory tunnel eg.

C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel

rather than

C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel_files

where you seem to have put them. A way around this is

1. Create the tunnel folder in the correct place (and any subfolders)

2. Remove the final folder from your workspace mapping so

   //tunnel/... //wtansill_localhost_1666/tunnel/... becomes //tunnel/... //wtansill_localhost_1666/...

this would mean anything under

C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel_files

would be mapped to //tunnel/tunnel_files which is I think what you want.

Hope this helps.