If we assume that the executor defines which name is used for the workspace directory then this is causing similar problems for p4-plugin. The number appended to the directory for each executor (e.g. job-name@1) is not consistent with EXECUTOR_NUMBER. This makes it almost impossible to stop contamination of workspaces when concurrent builds occur. Increasing the priority. We see this on 2.138.2.
Freestyle (p4-jenkins terminology) job. Build on slave only (unix slave with 4 executors, Using "_" instead of "@" for workspace separator). Concurrent jobs allowed.
Simple sync of stuff, build script is:
# sleep to see how concurrent builds behave
Conclusion: no correlation between EXECUTOR_NUMBER and workspace directory.
Especially of note:
build 4 has executor 2 and syncs to workspace/stream-simple-ant_4
build 5 has executor 2 and syncs to workspace/stream-simple-ant_2
Test is to "build now" 4 times in quick succession so that all are running at the same time.