|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This issue has just occurred for me also, so it must be a perforce option as I get exactly the same string.
For me
p4 where
works fine
p4 where //...
comes back with:
Some commands just want to watch the database churn. Fix your workspace mapping.
Are these command not equivalent? Is p4 where less intensive that p4 where //... and that is why our servers are complaining
Tom