Hi Jerry, Mainly 3 things:
- an [auth] section with credentials so that the slave can authenticate to our mercurial server (RhodeCode) - an [extensions] section to enables all required extensions such as largefiles - a [subpaths] section with the mapping to all our subrepos This file is managed with puppet, so whenever for example a subrepo is added or relocated, or a new extension is necessary on build slaves, it's easy to propagate the changes. I hope this satisfies your curiosity. Olivier On Monday, June 24, 2013 10:39:53 PM UTC-4, Jerry wrote: > > Hi, Olivier. Just out of curiosity, what sorts of things do you put in the > ini file on a build slave? We mostly put human-user-specific things in our > ini files for Mercurial (hooks, usernames, etc.) and I'm wondering how you > use this in a Jenkins context. > > Thanks! > -- Jerry > > > > On Friday, June 21, 2013 3:18:43 PM UTC-4, Olivier Trempe wrote: >> >> Hello everyone! >> >> Here's the solution to a lingering and unsolved problem (at least, there >> is no satisfying answers to me): >> >> *Where do I put my mercurial.ini file on Jenkins slaves running as >> windows service?* >> * >> * >> Depending on your OS, here are the possible answers >> >> *C:\Documents and Settings\NetworkService\mercurial.ini (WinXP) * >> *C:\Windows\System32\config\systemprofile\mercurial.ini (Win7)* >> >> On WinXP, it could also be in: *C:\Documents and >> Settings\LocalService\mercurial.ini (WinXP)* >> >> Those NetworkService and LocalService dirs are hidden system dirs. >> >> I did not test all possibilities, but for me, it works. It may be a >> little different for you, but it gives you a good starting point to find >> where it should be. >> >> Enjoy! >> >> Olivier Trempe >> >> >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
