[
https://issues.jenkins-ci.org/browse/JENKINS-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-13329.
--------------------------------------------
Resolution: Fixed
> Mercurial debug causes clone repository each time Mrather than update
> ---------------------------------------------------------------------
>
> Key: JENKINS-13329
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13329
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Affects Versions: current
> Environment: Linux, Jenkis 1.458, mercurial 1.7
> Reporter: Vladimir Kralik
> Assignee: Kohsuke Kawaguchi
> Priority: Minor
>
> JENKINS-4672 gives possibility to setup Marcurial debug flag.
> When I switch it on, the all mercurial call is done with option "--debug".
> The first command, during the build, checks if configuration of repository
> wasn't changed.
> This check is done by comparision result of commad "hg showconfig
> paths.default" with jenkins configuration.
> But there is a different output if the debug option is ON.
> Without debug option :
> $ hg showconfig paths.default
> https://hg/hg/zpis
> With debug option :
> hg --debug showconfig paths.default
> read config from: /etc/mercurial/hgrc
> read config from: /data/hudson/.hgrc
> none: https://hg/hg/zpis
> So with the debug option, the mercurial configuration is always different as
> jenkins configuration.
> Result is :
> -----------
> Building in workspace /data/hudson/jobs/vlk-pokus/workspace
> [workspace] $ hg --debug showconfig paths.default
> read config from: /etc/mercurial/hgrc
> read config from: /data/hudson/.hgrc
> none: https://hg/hg/zpis
> which looks different than https://hg/hg/zpis
> so falling back to fresh clone rather than incremental update
> Workaround : Switch off the degug option.
--
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
