Commit access (level 3) for Kagami :saschanaz (saschanaz@outlook.com )
Categories
(Infrastructure & Operations :: Infrastructure: LDAP, task)
Tracking
(Not tracked)
People
(Reporter: hsinyi, Assigned: htusiime)
Details
Attachments
(1 file)
747 bytes,
text/plain
|
Details |
Kagami's level 1 was granted in bug 1547165.
We'd like to ask for Level 3 access for Kagami that they can check-in their patches.
Comment 1•5 years ago
|
||
I have read, and agree to abide by, the Commit Access Requirements.
Comment 2•5 years ago
|
||
Vouching for the requested commit access for Kagami.
Comment 3•5 years ago
|
||
I vouch too!
Comment 4•5 years ago
|
||
(I think this is on the wrong component)
Reporter | ||
Comment 5•5 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #4)
(I think this is on the wrong component)
oops, this wasn't the component I was really thinking of! And thank you Emilio.
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Hello Kagami,
Commit access level 3 has been granted. +level_2, +level_3.
It may take up to 1hr for the account changes to propagate. Then you can log out and back in to SSO.
Please confirm here that you have access so we can close this bug.
Thank you.
Comment 7•5 years ago
|
||
Hello, hg.mozilla.org says I have the right permission:
A SSH connection has been successfully established.
Your account (saschanaz@outlook.com) has privileges to access Mercurial over
SSH.
You are a member of the following LDAP groups that govern source control
access:
scm_level_1, scm_level_2, scm_level_3
This will give you write access to the following repos:
Firefox Repos via Lando, Project Repos (projects/), Try, User Repos (users/)
You will NOT have write access to the following repos:
Autoland (integration/autoland), Firefox Repos via direct push, Localization Repos (releases/l10n/*, others), Version
Control Tools (hgcustom/version-control-tools)
You did not specify a command to run on the server. This server only
supports running specific commands. Since there is nothing to do, you
are being disconnected.
Connection to hg.mozilla.org closed.
But Lando still says I have no Level 3 access. Maybe because Lando uses LDAP account there? What should be done?
Assignee | ||
Comment 8•5 years ago
|
||
Hi Kagami, this may be a duplicate if you have already done this, but can you please try logging out of SSO and logging in again?
Comment 9•5 years ago
|
||
Logged in again in SSO and went to Lando again and it still says I need Level 3 access. Not sure why.
Assignee | ||
Comment 10•5 years ago
•
|
||
Ok, thank you for trying that. I've reached out to the Lando team and I'll get back to you as soon as they respond.
Assignee | ||
Comment 11•5 years ago
|
||
Hi Kagami, can you confirm that when you log in to Lando you are using the community account, and not your employee account? The Lando permissions won't work on that account.
Or if you prefer to use the employee @mozilla.com account, we can transfer the permissions to that one.
Comment 12•5 years ago
|
||
I was using my employee account. It's confusing that I have two accounts there 😅
I prefer my mozilla.com account, because if not other Mozilla services tries to log in automatically with my community account. Does the transfer affect email info of my commits?
Thanks!
Updated•5 years ago
|
Assignee | ||
Comment 13•5 years ago
|
||
Hi Kagami,
For your email info, you will need to change ~/.ssh/config file and replace your community email with your Mozilla email. Before we proceed with this change to your employee account we'll need to verify some identity information. Can you send the following information to hamilton@mozilla.com from your employee email?:
- The asset tag# of your Mozilla-issued laptop
- Phone number of the duo device used for Duo Push
After verification, I'll add Commit Access Level 3, HG access, and the ssh key to your employee LDAP and remove them from your community account. We'll finally confirm your access then close this out.
Assignee | ||
Updated•5 years ago
|
Comment 14•5 years ago
•
|
||
Hi Hamilton,
Just to make sure, it's hamilton@, not htusiime@, right?
Will the author information on my commits change after this? I prefer not, and I assume it won't, just to make sure again.
Assignee | ||
Comment 15•5 years ago
|
||
Either will work (they both point to me).
For your authoring commit information, that actually would come from that config file from above. If you leave that as "saschanaz@outlook.com" the commit author will remain stay the same; you will just be logging into Lando (and other SSO'd services) with your MoCo email.
So I will leave both community account and the MoCo account with commit access. Once I recieve that information from you we'll apply the changes so you can test.
Assignee | ||
Comment 16•5 years ago
|
||
Hi Kagami,
Commit Access Level 3 has been granted on your MoCo account. It may take up to 1hr for these changes to sync.
Then please log out and log into SSO for your MoCo account and try accessing Lando.
Please also check your hg.mozilla.org scm permissions as previously done.
If possible, you may want to do a test commit.
When everything looks good please let us know
Thanks
Comment 17•5 years ago
|
||
Thanks, I confirmed that Lando works and hg.mozilla.org reports my permissions as expected.
Didn't do a test commit as I don't know how to do it 👀. Could you point me to a relevant documentation?
Updated•5 years ago
|
Assignee | ||
Comment 18•5 years ago
|
||
Hi Kagami, unfortunately we are unable to provide support performing actions within the scm environment. If you have not already, you can join Mozilla's developers chat forum "Matrix", and open the #vcs channel to ask.
Matrix Signup: https://wiki.mozilla.org/Matrix
#vcs Support channel: https://chat.mozilla.org/#/room/#vcs:mozilla.org
As your configuration has been completed, we'll close out this request for now. If you find or are recommended more account changes by those in Matrix#vcs, as a Mozilla employee you can reach out to me on Mozilla Slack @TheAurian for live chat support.
Thank you.
Description
•