Since updating to 1.17.3, clean builds consistently started failing with:

P4JAVA: Error(s): Lobby.meta corrupted during transfer (or bad on the server)
84546070BA73F1D0629D10E238561CC6 vs 610127BF50C89DAFAAFD37684089F638

The second hash matches the MD5 stored on the server (confirmed with p4 verify).
Manually running p4 sync -f on the same machine works fine, same thing if using the P4V visual client.
Downgrading to 1.17.2 resolves the issue.

Steps to Reproduce

1. Configure a Jenkins job with P4 Plugin 1.17.3, Manual (custom view) workspace, Line Endings: LOCAL, on a Windows build agent, with Linux servers for the Perforce and Jenkins controllers.
2. Enable force sync (delete workspace + force sync option)
3. Trigger a build syncing a depot that contains files of type text (unclear if any text files are affected, the consistent failure we had was always the same text file)
4. Observe checksum mismatch error during sync

Given the fact we're mixing Windows machines with Linux ones in our environment, line-endings or case sensitivity could be potential culprits.

11:53:24 ...   View: +
11:53:24 
11:53:24 P4 Task: establishing connection.
11:53:24 ... server: jupiler:1667
11:53:24 ... node: delirium
11:53:24 
11:53:24 P4 Task: syncing files at change: 748633
11:53:24 ... p4 sync -f -q D:\ws/ActionSystemExample/pc_bootstrapped/...@748633
 +
11:55:55 P4 Task: attempt: 1
11:55:58 ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s):
11:55:58 Lobby.meta corrupted during transfer (or bad on the server) 84546070BA73F1D0629D10E238561CC6 vs 610127BF50C89DAFAAFD37684089F638
11:55:58 
11:56:00 Triggering a new build of TyreKick Build Fail
11:56:00 Finished: FAILURE