- Can multiple P4 verify processes run in parallel?
Yes, you may use all sort of ways such as GNU parallel, & operator, etc, to run P4 command in parallel, with your own risk of hitting weird issue if their verification is somewhere overlapped.
- Does p4 verify -q //... check all files, including submitted files(archive files), shelved files, files in the unload depot, and files in the archive depot(archived files)? What commands should I run to ensure that I check every single file?
No, p4 verify -q //... does not check all files in all scenarios. Here's what it covers:
Submitted files (archive files): Yes, it verifies the MD5 checksum and/or file size of submitted files present in the depot.
Shelved files: No, p4 verify does not verify shelved files. Shelved files are not part of the verification process.
Files in the unload depot: No, files in the unload depot (e.g., files from unloaded workspaces) are not verified by default.
Files in the archive depot: Yes, archived files (e.g., files moved to the archive depot using p4 archive) are verified.
- Could you clarify the scenarios for using the -s parameter? My understanding is that the -s verifies both the file size and the MD5 checksum, while without it, it only verifies the MD5. Is that correct?
Your statement is correct.
For when to use -s, Some examples might be, say, if you suspect file size issues or if you want a stronger verification process that checks both file content (MD5) and size.
- When users submit files, is the file's MD5 automatically generated and saved on the server？ And what is the -u option used for in p4 verify?
Yes, when a user submits a file to the Perforce server, the server automatically computes an MD5 checksum for the file and stores it in the metadata database. This checksum is later used for verification during commands like p4 verify.