[
https://issues.jenkins-ci.org/browse/JENKINS-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jglick resolved JENKINS-1420.
-----------------------------
Resolution: Duplicate
Possibly resolved by the fix of JENKINS-13400. If the problem persists in the
future, reopen (or file a new bug) and include the portion of the build log
that says "...which looks different than..." as that will indicate how to write
a test for the problem.
> Local repo location string not aggressively normalized
> ------------------------------------------------------
>
> Key: JENKINS-1420
> URL: https://issues.jenkins-ci.org/browse/JENKINS-1420
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: medotin
> Assignee: jglick
> Priority: Minor
>
> This is v1.8 of the Mercurial plugin, and (though I believe it's irrelevant)
> 1.186 of hudson.
> I'm running Hudson on the same machine as my hg repo. I entered the path to
> my
> repo as /xyz. The first build was fine, but because the cloned repo's hgrc
> file
> listed the repo location as c:\xyz,
> hudson.plugins.mercurial.MercurialSCM.checkout saw these two strings as
> different and tried to do a clone instead of an update. It correctly did an
> update once I changed my hudson config repo string to c:\xyz to match hgrc.
> Perhaps there's some normalization to be done on local repo paths.
> On a side note, and I haven't looked into this, when it was trying to do the
> clone via first doing a delete, it could not delete the hgrc file (using
> Windows). However if I deleted hgrc manually, then ran the build, it deleted
> the rest of the stuff just fine. Seems like a bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
