|
||||||||
|
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, send email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
That's a 'sync' command, not a 'where' command. The reason 1.2.9 works for you is because that version does not try to obtain the 'where' map.
Ask your perforce administrators if they have any triggers that contain the phrase: "Some commands just want to watch the database churn." I have downloaded 2012.2, and have confirmed that this is NOT an error built-in to perforce, which means your admins are doing something to intentionally block certain commands.