Skip to content
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.

Hg Authentication Issues #4

Open
GoogleCodeExporter opened this issue May 10, 2015 · 0 comments
Open

Hg Authentication Issues #4

GoogleCodeExporter opened this issue May 10, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

If you have an Hg repository in your project, you might run into authentication 
issues when Moe tries to clone the Hg repo in HgClonedRepository's 
cloneLocallyAtTip(...) method. Moe tries to clone an Hg repo anytime you try to 
create_codebase, change, or migrate with an Hg repository.

What happens is Moe runs "hg clone" on your repo, but when the repo asks for 
your username and password, Moe crashes instead of letting you enter them.

A temporary solution is to have in your ~/.hgrc a section as follows:

[auth]
moe.prefix = https://path/to/repo
moe.username = [email protected]
moe.password = password

The "moe" before the prefix/username/password can be anything as long as it is 
consistent among the three fields. Make sure the prefix is the same URL as the 
one specified in the moe_config for your Hg repository.

By putting your authentication info in the .hgrc, you shouldn't have to input 
it when "hg clone" is run.


Original issue reported on code.google.com by [email protected] on 25 Aug 2011 at 7:53

cgruber added a commit to cgruber/MOE that referenced this issue Feb 19, 2019
Refactor config objects and deal with the fallout
cgruber added a commit to cgruber/MOE that referenced this issue May 11, 2022
Bump bazel maven repository.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant