-
Bug
-
Resolution: Unresolved
-
Major
-
None
We’ve upgraded our perforce from 2012.1 to 2012.2, which supports ssl. But with the new version, the perforce plugin is having problem before the sync. It’s trying to run “p4 where” command at // level, instead of the changelist. This was a fixed bug back in 2011 in v1.2.9, which worked with the latest 2012.2. However, the newer 1.3.x won’t work. 1.3.x work fine with perforce 2012.1 with no problem. Upgraded to the latest jenkins, but no difference.
copying a segment of the log:
===
Started by user admin
Building remotely on blinnv12g in workspace /scratch/linux86/jks/perforce_test2/dev
Using remote perforce client: jkspilot2_p4-161040911
[dev] $ /usr/local/bin/p4 workspace -o jkspilot2_p4-161040911
[dev] $ /usr/local/bin/p4 login -p
[dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx workspace -o jkspilot2_p4-161040911
Last build changeset: 277259
[dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx counter change
[dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -s changes //jkspilot2_p4-161040911/...@277260,@277278
[dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx describe -s 277277
[dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -G where //...
Caught exception communicating with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn.
com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn.
at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:159)
at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:82)
at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:71)
at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:425)
at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:662)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1325)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
at hudson.model.Run.execute(Run.java:1543)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
ERROR: Unable to communicate with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn.
Email was triggered for: Failure
Sending email for trigger: Failure
Sending email to: s@xxx.com
Finished: FAILURE
===
Where command has always been executed at that level, and will only ever return the Depot<>View<>Workspace map. This is a very low intensity command that simply generates a more useful version of your view. I invite you to try it for yourself.
The issue is that your perforce server or client is returning an error with junk data: "Some commands just want to watch the database churn."
I'm assuming this is part of some trigger that you or your administrators have added. You will need to remove it.