Re: [p4] p4 command line sync not working sometimes

Sambwise <[email protected]> Fri, 11 May 2018 13:30:01 -0700
Newsgroups gmane.comp.version-control.perforce
Message-ID <[email protected]>
Posted on behalf of forum user 'Sambwise'.

IMO this sounds like an issue that's worth investigating.  Do you
know why the files would be getting modified?  Can the pipeline modify
the files that were synced?  If so, should those modifications ever be
submitted or should they always be discarded?  Is it possible that
another user has access to these files?  Are you attempting to re-use
the same client spec across multiple client hosts?  Etc.

If the issue is that the pipeline is modifying the files and you don't want
to keep those modifications (this sounds really gross btw -- your build system
shouldn't be modifying your source files), then "sync -f" will fix
it at the cost of re-syncing all the other files.  A more performant
solution might be "p4 clean", which will only sync the files that were
modified.

If there's some other issue (like the client spec being shared), "p4
sync -f" will work around it in this particular instance, but will probably
cause other issues elsewhere (i.e. wherever else the client spec is being
shared).



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5728-p4-command-line-sync-not-working-sometimes
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user