I think this is the 5th time I’ve had to figure this out in the past few years, so this time I’m going to preserve it here for posterity
The problem is usually one or more of:
- You have files missing from your workspace that need replaced.
- You have locally modified (i.e. not opened for edit) files that need replaced.
- These files are large in either size or number, and on a slow or remote server, so a complete force-sync is not an appealing option.
Normally this could easily be solved with something like p4 diff -sd/-se //depot/path/.. | p4 -x – sync -f, which finds all the missing/outdated files and then force-syncs them.
The problem with this approach comes when you need the files from a specific revision or label. While you can pass in a label/revision to ‘p4 diff’, the sync part will always retrieve the latest version of a file. To fix this we need to save the list of files we need to a temporary location, then postfix each line with the version we want, then feed that new list back to p4 sync.
But there’s one final catch. If your filenames are local paths instead of Perforce paths, you cannot specify a label, only revisions. E.g. c:\temp\foo.dat@SOME_LABEL will not work, but c:\temp\foo.dat#999 will. Fortunately we can use the pseudo revision ‘have’ for our purposes.
REM Could optionally pass these as %1 and %2 from the cmd line
echo Setting ‘have’ to %LABEL% for %BASE_DIR%
REM do a nop sync that sets our ‘have’ version to the label we want
p4 sync -k %BASE_DIR%%LABEL%
echo Finding modified files..
p4 diff -se %BASE_DIR%%LABEL% > p4diff.txt
echo Finding missing files..
p4 diff -sd %BASE_DIR%%LABEL% >> p4diff.txt
echo Building sync commands
REM Append #have to each filename and put them all in a list of files to sync
for /f %%i in (p4diff.txt) Do echo %%i#have>> p4sync.txt
REM Now sync everything
if exist p4sync.txt (
p4 -x p4sync.txt sync -f
echo It seems no files need updated!
- Top 10 Popular UX & UI Design, Prototype and Blueprinting Tools - February 25, 2022
- Topics to learn in Prometheus with Grafana Training - February 24, 2022
- DevSecOps Engineers Roles and Responsibilities - February 23, 2022