When running concurrent builds of the same job (2 in our case) on the same slave, the cleanup plugin cleans up workspace affecting both job. We were under the impression that with concurrent builds jenkins creates different workspaces for isolation.

jenkins concurrent build doc: 'When Jenkins creates different workspaces for isolation, Jenkins appends "@num" to the workspace directory name, e.g. "@2"'