Closed Bug 658396 Opened 13 years ago Closed 13 years ago

Mercurial commit access/LDAP flags for new web developer

Categories

(mozilla.org :: Repository Account Requests, task)

All
Other
task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: tofumatt, Assigned: ebalangue)

References

Details

Attachments

(1 file)

Attached file ssh public key
I need write access to mercurial so I can commit to nightly.mozilla.org. I also need access to people.mozilla.com and some other servers that Dave will supply.

Attached is my public key.
cm-webdev01-master01
khan
cm-vpn01
Assignee: desktop-support → shui
CC'ing Erica (she just got my contributor's agreement).
Your ssh key has been added which will grant you access to people.mozilla.com ,cm-webdev01-master01, khan and cm-vpn01.

You should file a new bug for mercurial under repository account requests component.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
I have received Matthew's Committer's Agreement.
Group: infra
Bug reopened in reply to Bug 658619. His ssh key wasn't configured, only mercurial.
Assignee: shui → ebalangue
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Matthew's ssh key has been added to his account, this bug shall close out. Feel free to contact us for any questions.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
I can't seem to ssh into hg.mozilla.org, and if I try to push via https I get an SSL Required error back from Mercurial.

Are my keys on hg.mozilla.org?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Blocks: 648002
Severity: critical → blocker
HG uses the keys from LDAP, so there's no separate setup needed.

Have you set up your ~/.ssh/config per https://developer.mozilla.org/en/Mercurial_FAQ#Required_configuration ?

If so, pastebinning the output of ssh -v hg.mozilla.org might be enlightening.
With everything setup as prescribed in the Mercurial FAQ I still get: http://pastebin.mozilla.org/1250424

My .hg/hgrc looks like this:

[paths]
default = https://hg.mozilla.org/webtools/nightly/
default-push = ssh://hg.mozilla.org/mozilla-central/
You probably want to use ssh://hg.mozilla.org/webtools/nightly/ as your default-push for that repo, but otherwise things should be OK (assuming you have the right username in your ~/.ssh/config - full LDAP address including "@mozilla.com").

Eljon should be able to confirm that your account is set up properly, it's possible something's just missing on their end.
Yup, ~/.ssh/config is:

Host hg.mozilla.org
User mmacpherson@mozilla.com

My default-push is ssh://hg.mozilla.org/webtools/nightly/ in hgrc. I must've copied that from the wrong window or something; my bad.

When I run hg push I get:
pushing to ssh://hg.mozilla.org/webtools/nightly/
remote: Permission denied (publickey,gssapi-with-mic).
abort: no suitable response from remote hg!

Let me know if there's anything else I can do or if it's just something missing on ops' end. Thanks for the help so far!
Hi Matthew, your credentials have been updated. Feel free to test your account. Also, reopen the bug and contact us for any issues that may arise from hereon.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Hi again.

I am now able to ssh into hg.mozilla.org but when I try to push I get the following error:

~/sites/nightly% hg -v push                                                
pushing to ssh://hg.mozilla.org/webtools/nightly/
running ssh hg.mozilla.org "hg -R webtools/nightly/ serve --stdio"
searching for changes
1 changesets found
remote: abort: could not lock repository /repo/hg/mozilla/webtools/nightly/: Permission denied
abort: unexpected response: empty string
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hi Matthew, we've checked into your ldap credentials and we have commit access level 1 for your account. Is this the commit access level necessary for your work?
Status: REOPENED → NEW
Severity: blocker → major
https://hg.mozilla.org/webtools/nightly/ is level 2, presumably. Bug 658619 was field for SVN access. HG access and SVN access are handled separately - presumably HG access was never enabled.

Eljon, can you please ensure that Matthew has hg/level_2 bits set?

Sorry this process has been bumpy, Matthew. The fact that this request was made in two bugs (one of which was in the wrong component and initially hidden) kind of confused things. There's a defined process for account requests but it's not necessarily intuitive (though it is documented at http://www.mozilla.org/hacking/committer/ ).
Component: Server Operations: Account Requests → Repository Account Requests
QA Contact: mrz → repo-acct-req
Gavin Matthew now has hg/level 2 access under his account. We do apologize for this issue. Feel free to contact us for your questions, this bug is closing out.
Status: NEW → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: