Jobs fail if they are allowed to run concurrent if svn commands are used in the build steps like shell/windows batch.

Reason is the "@" appended to the workspace name which indicates svn pegging.
All jobs running in "workspace" succeed all jobs running in "workspace@2" and upwards fail with the message "is not a working copy"