Steps to Reproduce:
1) Create a job using mercurial plugin, naming a given repository
2) run the job once (assume it succeeds)
3) delete the mercurial repo on the hg server
4) recreate the mercurial repo on the hg server
5) wait for the Mercurial Polling to occur on Jenkins

Actual Behavior:
The polling fails because the repository is unrelated to the original repo:

Mercurial Polling Log
Started on Feb 26, 2013 10:03:02 AM
[workspace] $ hg pull --rev default
pulling from http://cm5/hg/android/v01.1/trunk/
searching for changes
abort: repository is unrelated
[workspace] $ hg log --rev default --template

[workspace] $ hg log --rev default --template

Done. Took 0.94 sec
No changes

Expected Behavior:

• The workspace is automatically wiped
• the repository is re-cloned
• the job is triggered

Notes:
I assume this is a rare scenario. I only encountered it during some testing that I was performing which required me to create, delete and re-create the mercurial repository.

Thanks,
John