Perforce Polling is failing all of a sudden

[ShobhaD]

Hi All,

Since this morning, perforce polling is failing for all the jobs
that have the feature enabled. A manually fired build is running fine.
Even though there are no changes it would say so.


Started on Jan 6, 2011 12:25:52 PM
Looking for changes...
Using node: node-name
Using remote perforce client: workspace-name
[Job Name] $ "C:\\Program Files\\Perforce\\p4.exe" workspace -o
workspace-name
[Job Name] $ "C:\\Program Files\\Perforce\\p4.exe" login -p
[Job Name] $ "C:\\Program Files\\Perforce\\p4.exe" -P
D488C2D802DBEA20F93031923AF9B67E workspace -o workspace-name
Saving modified client workspace-name
[Job Name] $ "C:\\Program Files\\Perforce\\p4.exe" -P
D488C2D802DBEA20F93031923AF9B67E -s client -i
Last sync'd change was 7799797
[Job Name] $ "C:\\Program Files\\Perforce\\p4.exe" -P <hash of
perforce port> changes -m 2 //workspace-name/...
ERROR: Failed to record SCM polling
java.lang.NumberFormatException: For input string: "level"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.<init>(Unknown Source)
at
com.tek42.perforce.parse.Changes.getChangeNumbers(Changes.java:144)
at hudson.plugins.perforce.PerforceSCM.needToBuild(PerforceSCM.java:
897)
at hudson.plugins.perforce.PerforceSCM.pollChanges(PerforceSCM.java:
793)
at hudson.scm.SCM.poll(SCM.java:372)
at hudson.model.AbstractProject.poll(AbstractProject.java:1205)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:417)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:446)
at hudson.util.SequentialExecutionQueue
$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

[Rob Petti]

Have you changed the security level on your server recently? It's possible that it doesn't like the ticket-based authentication that the plugin is doing.

I've been meaning to bring some sanity to the error output of the plugin, but haven't really gotten around to it. If you are still having trouble by next week, then I should have a new release that will give more meaningful log information.

~Rob

PS. That hash is the authentication ticket retrieved during login, not the hash of the perforce port.

[ShobhaD]

Looks like that was exactly the problem.
Our perforce administrator added users to the broker config file to
allow the changes command to run unfiltered. This worked and SCM
polling is back again.

Thanks Rob !

-Shobha