[p4] Perforce Sync does not always work...
heinz2 at llnl.gov
Wed Jul 26 11:10:01 PDT 2000
You can just sync the changed files if you are willing to run a p4 diff
on the fileset.
To force a sync on a file edited out of perforce control:
p4 diff -se ... | p4 -x - sync -f
To force a sync on a file deleted out of perforce control:
p4 diff -sd ... | p4 -x - sync -f
Is this what you are talking about?
Jeremy Russell wrote:
> I am continually frustrated by the fact that "p4 sync //depot/tree/dir/..."
> does not always sync all the changed files. In order to be sure that I will
> be syncing all the changed files I am very often forced to add the "-f"
> option to the sync and do an entire bring over to be sure that I have gotten
> all the changes.
> This is very frustrating because of the code build times we encounter. At
> this time, because we cannot trust "p4 sync" to bring over every changed
> files, so we sync an entire code line from Perforce each time we do a build,
> meaning that 40% to 50% of build time is because of syncing. Additionally,
> these syncs are between the range of 20,000 to 30,000 files and 100's of MB.
> We are working on some solutions involving keeping track of change lists and
> syncing a range of change lists instead of file specs, but this does not
> solve the basic issue that "p4 sync" does not work.
> I am wondering if anyone else out there has similar issues with "p4 sync"
> and what you do to deal with it.
> Jeremy Russell
> Release Engineering
> ChannelPoint, Inc
> jrussel at channelpoint.com
> AOL\IM jrussel21
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user