Hi Jesse,

all of the described locations didn't work for our case. We wanted to use 
the registry key, but for whatever reason this didn't work either.
Finally we used HGRCPATH environment variable which worked for us.
Unfortunately this is a pretty harsh override, so we had to additionally 
create the .hg/hgrc files in the hg installations (with the hgrc file 
being simply the default config from the installation with another name).

Thanks alot for the help!
 
Andreas Schilling
CAE Processes & Data Management
-------------------------------------------------------------------
Dipl. Inf. Andreas Schilling
Senior Software Architect

TWT GmbH
Science & Innovation
Bernhäuser Str. 40 - 42
73765 Neuhausen
 
Tel: +49 - 7158 - 17 15 - 673
E-Mail: [email protected]
--------------------------------------------------------------------
www.twt-gmbh.de
--------------------------------------------------------------------
Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (stv.)
Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778
Umsatzsteuer: ID-Nr.: DE147841145
--------------------------------------------------------------------



Von:    Jesse Glick <[email protected]>
An:     [email protected]
Datum:  18.07.2012 00:12
Betreff:        Re: Jenkins as Windows Service; Mercurial.ini
Gesendet von:   [email protected]



On 07/17/2012 07:56 AM, Andreas Schilling wrote:
> our jenkins master is set up as windows service using the windows local 
system account.
> where are we supposed to put the mercurial.ini with the credentials for 
the https access?

hgrc(5) [1] gives a number of locations where Mercurial looks, or can be 
made to look, for config files.

You can also pass '--config section.key=value' as part of the Mercurial 
command, so defaults could be configured in the Mercurial installation 
your jobs use (see 
$jenkins/configure). Of course this is less secure than storing 
credentials in a local file location; for example, the values will 
probably appear in build logs.

By the way if you are trying to use client certificates, rather than just 
a username/password combo, and get it to work, please update JENKINS-7351 
[2] accordingly.

[1] http://www.selenic.com/mercurial/hgrc.5.html
[2] https://issues.jenkins-ci.org/browse/JENKINS-7351

Reply via email to