![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Jesse Glick
|
|
Components:
|
mercurial |
|
Created:
|
26/Feb/13 6:18 PM
|
|
Description:
|
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 {node}
[workspace] $ hg log --rev default --template {rev}
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
|
|
Environment:
|
Jenkins 1.502 Mercurial Plugin 1.43
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
John A
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
