Closed Bug 728306 Opened 12 years ago Closed 12 years ago

Commit Access (Level 2) for Vlad Maniac: mozmill-tests and litmus-data commit

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u279076, Assigned: marcia)

References

Details

Attachments

(1 file, 1 obsolete file)

Please grant Vlad Maniac Level 1 commit access to hg.mozilla.org/qa/mozmill-tests and hg.mozilla.org/qa/litmus-data. He has indicated to me that he has read and understands the commit policy.

Vlad, please attach your SSH public key and indicate the email you wish to use for commits.
Actually, based on my own bug from 2 years ago (bug 582402) Vlad needs Level 2.
Summary: Commit Access (Level 1) for Vlad Maniac: mozmill-tests and litmus-data commit → Commit Access (Level 2) for Vlad Maniac: mozmill-tests and litmus-data commit
His key is in bug 704799. So just need the module owner to vouch and we can move this one over.
I think Anthony counts as a module owner for the relevant repositories.

server-ops, please add hg/scm_level_[12] bits!
Assignee: mozillamarcia.knous → server-ops
Yup, I am module owner for mozmill-tests and litmus-data. I vouch for Vlad.
Attached file ssh public key (obsolete) —
E-mail: maniacvld@gmail.com 

Or should I use the LDAP ? see bug 704799
Yeah, use your LDAP since you already have the key and SVN access setup there.
I enabled scm level 1&2 for you.
Be good ;)
Assignee: server-ops → dgherman
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I have some problems using my commit access. 

I get this error 

vladmaniac@p4509:~/Desktop/land2/mozmill-tests$ hg push
pushing to http://hg.mozilla.org/qa/mozmill-tests/
searching for changes
remote: ssl required

I made all the settings with Anthony, so it seems I might have a problem with the key, probably because the key was generated for the gmail address and i got my access for LDAP
Is there any way the server-side key can be updated to use Vlad's gmail address? 
maniacvld@gmail.com

This way his ability contribute is not specifically tied to having LDAP access.
The ability to commit to Mozilla repositories *is* tied to having an LDAP account.
However, the SSH keys are not tied to an email address, per se. The email address can be attached as a comment at the end of the key, and it does not matter in terms of authentication.
Make sure your settings are correct. Provide more verbose logs. I have double checked and your account should work.
These are the settings you need to land a patch 
https://developer.mozilla.org/en/Mozmill_Tests/#Landing_of_patches

I have reviewed the steps with Anthony, they are no rocket science nevertheless. 
I can't think why it echoes the error in comment 8 

Can we change the ssh key? I'll attach a new one
Assignee: dgherman → nobody
Component: Repository Account Requests → Release Engineering: Developer Tools
QA Contact: repo-acct-req → lsblakk
Assignee: nobody → mozillamarcia.knous
Component: Release Engineering: Developer Tools → Repository Account Requests
QA Contact: lsblakk
Attached file ssh public key 2
Attachment #598805 - Attachment is obsolete: true
Mu .ssh directory looks like this 
http://pastebin.mozilla.org/1498509
Should you guys be needing other info from my system, please ask specifically
I think you need to use https as the error says:

remote: ssl required

The wiki link you pasted uses https:

[paths]
default = https://hg.mozilla.org/qa/mozmill-tests
default-push = ssh://hg.mozilla.org/qa/mozmill-tests/
(In reply to Ashish Vijayaram [:ashish] from comment #15)
> I think you need to use https as the error says:
> 
> remote: ssl required
> 
> The wiki link you pasted uses https:
> 
> [paths]
> default = https://hg.mozilla.org/qa/mozmill-tests
> default-push = ssh://hg.mozilla.org/qa/mozmill-tests/

Please see the link in comment 11
Nevertheless, I did the changes you suggested but I get the same results. 

Thanks for jumping in:)
I want to do more checks before switching the SSH key. The symptoms do not indicate that's the issue.
Vlad, how does the .hgrc file looks like? Can you copy/paste it here?
Also, what happens when you "ssh -v hg.mozilla.org"?
Thank you.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Global .hgrc file: 

[ui] 
username = Vlad Florin Maniac <vmaniac@mozilla.com> 
merge = internal:merge   

[diff] 
git = 1 
showfunc = 1 
unified = 8  

[defaults] 
qnew = -U  

[extensions] 
hgext.mq =  

[hooks] 
prechangegroup.mq-no-pull = ! hg qtop > /dev/null 2>&1


local .hgrc file: (under mozmill-tests/ folder) 

[paths]
default = https://hg.mozilla.org/qa/mozmill-tests
default-push = ssh://hg.mozilla.org/qa/mozmill-tests/
-------------------------------------------------------------------
http://pastebin.mozilla.org/1504529

Hope that helps
According to comment 13, you are missing the .ssh/config file.
Take a look here: https://developer.mozilla.org/en/Mercurial_FAQ#Required_configuration
(In reply to Dumitru Gherman [:dumitru] from comment #19)
> According to comment 13, you are missing the .ssh/config file.
> Take a look here:
> https://developer.mozilla.org/en/Mercurial_FAQ#Required_configuration

I did have it when I did the commit tutorial with Anthony. There was the same result
Assignee: mozillamarcia.knous → security-assurance
Status: REOPENED → ASSIGNED
Component: Repository Account Requests → Security Assurance: Incident
QA Contact: mcoates
Wrong component. Security Assurance: Incident is for security compromises that need investigation.

Moving back to Repository Account Requests
Assignee: security-assurance → mozillamarcia.knous
Component: Security Assurance: Incident → Repository Account Requests
QA Contact: mcoates → repo-acct-req
(In reply to Maniac Vlad Florin (:vladmaniac) from comment #20)
> (In reply to Dumitru Gherman [:dumitru] from comment #19)
> > According to comment 13, you are missing the .ssh/config file.
> > Take a look here:
> > https://developer.mozilla.org/en/Mercurial_FAQ#Required_configuration
> 
> I did have it when I did the commit tutorial with Anthony. There was the
> same result

Can you put it back? It's a mandatory piece to get this working.
Vlad - Can you please answer Dumitru's question in Comment 22? Would like to get this bug off my radar since the account was basically created and we are just waiting for you to verify it works. thanks.
(In reply to Marcia Knous [:marcia] from comment #23)
> Vlad - Can you please answer Dumitru's question in Comment 22? Would like to
> get this bug off my radar since the account was basically created and we are
> just waiting for you to verify it works. thanks.

Hey marcia, I'll get to it as soon as I have some time, I hate stalling you guys but my commit access is less prior than a firefox memory leak for example :( 

Again, very very sorry
Vlad: If you're still having issues with your account, please open a new Mozilla::Server Ops Account Requests bug.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Depends on: 737790
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: