Intermittently, the Mercurial plug-in will attempt to clone to a workspace that doesn't exist because it is adding "@2" to the end of the workspace path. This results in a clone that is unexpected and unnecessary.

CONSOLE OUTPUT
--------------------------------------------------
13:55:22 Started by an SCM change
13:55:22 [EnvInject] - Loading node environment variables.
13:55:22 Building remotely on <NODE_NAME_REMOVED> in workspace /var/lib/jenkins/workspace/<JOBNAME_REMOVED>@2
13:55:22 Changing BUILD_ID variable (job build time) with the date pattern yyyy-MM-dd'T'HH:mm:ssZ.
13:55:22 $ /usr/bin/hg clone --rev default --noupdate http://<REPO_ADDRESS_REMOVED> /var/lib/jenkins/workspace/<JOBNAME_REMOVED>@2
14:24:19 Build was aborted
14:24:19 Aborted by <USERNAME_REMOVED>
14:24:19 Archiving artifacts
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern yyyy-MM-dd'T'HH:mm:ssZ.
14:24:19 adding changesets
14:24:19 adding manifests
14:24:19 adding file changes
14:24:19 transaction abort!
14:24:19 Recording test results
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern yyyy-MM-dd'T'HH:mm:ssZ.
14:24:19 No test report files were found. Configuration error?
14:24:19 Recording fingerprints
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern yyyy-MM-dd'T'HH:mm:ssZ.
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern yyyy-MM-dd'T'HH:mm:ssZ.
14:24:19 Description set: MERCURIAL_REVISION: ${MERCURIAL_REVISION}
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern yyyy-MM-dd'T'HH:mm:ssZ.
14:24:19 Finished: ABORTED