It looks like we are having the same issue here with this particular version (1.10.16).
Whenever we attempt to start a build we get the following output:
Started by user [snip]
Building in workspace [snip]
Connected to server: some.server.com:1666
Connected to client: some_client
SCM Task: cleanup workspace: [snip]
SCM Task: syncing files at change: 74
... sync [local-path/to/]...@74
... force update false
... bypass have false
ERROR: Unable to update workspace: com.perforce.p4java.exception.ConnectionException: For input string: "5869395008"
Finished: FAILURE
This is a very recent issue, builds issued last week using the same workspace worked just fine (polling interval: one minute with very few submits per week so far).
We are connected directly to the p4 server, there are no proxies nor brokers in between.
When issueing the following sync command directly from the machine Jenkins is working on (we build from master) it's clear that this workspace is far from synced:
> p4 -c some_client sync -n //...@74
//path/to/file#1 - added as local/path/to-file
...
I tried launching a build manually earlier today and this resulted in some of the files being synced: taking snapshots of the #have list for that workspace showed new files being added.
(p4 -c some_client //...#have > snap1.txt ; p4 -c some_client //...#have > snap2.txt ; diff --suppress-common-lines snap1.txt snap2.txt).
However the build would not start.
I managed to just clear the issue right now by modifying the workspace spec by suppressing the folder containing the files to sync (which were not needed for this build:
-//path/to/folder-with-files-not-synced/... //client/path/to/folder-with-files-not-synced/...
After modifying that line in the plugin settings the build started just fine after being launched manually.
Note that the problem occurred right after I modified the workspace spec thoroughly.
I went from that configuration:
//main/A/A1/... //some_client/A/A1/...
to this configuration:
//main/A/... //some_client/A/...
-//main/B/... //some_client/B/...
-//main/C/... //some_client/C/...
and the configuration which finally solved the issue was:
//main/A/... //some_client/A/...
-//main/A/A2/... //some_client/A/A2/... <- the added line, this folder contains a very large amount of files (several GB of data)
-//main/B/... //some_client/B/...
-//main/C/... //some_client/C/...
All these changes were done in the plugin configuration page (no edition from the p4 client).
I hope this helps.
Blocker
