[JIRA] [perforce] (JENKINS-21722) Unwanted -s (safe sync) flag is being passed to p4 sync

Fri, 07 Feb 2014 14:34:15 -0800

Jeff Ishaq commented on Bug JENKINS-21722

I think those are the global options you are referring to. The p4 sync operation appears to override these with its own variant of the -s flag, which is defined as follows:

The -s flag adds a safety check before sending content to the client
	workspace.  This check uses MD5 digests to compare the content on the
	clients workspace against content that was last synced.  If the file
	has been modified outside of Perforce's control then an error message
	is displayed and the file is not overwritten.  This check adds some
	extra processing which will affect the performance of the operation.
	Clients with 'allwrite' and 'noclobber' set do this check by default.


I am not sure from the ordering whether the "-s" flag is being passed to p4, or to p4 sync, in its usage above.  The slowness of the sync implies it's going to p4 sync, however.



(note that we are using "noallwrite" and "clobber" options, so the last bit about doing the check by default shouldn't apply here)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to