Closed
Bug 770576
Opened 12 years ago
Closed 12 years ago
change user name for releng mirroring account
Categories
(Developer Services :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: fox2mike)
References
Details
(Whiteboard: [reit])
Attachments
(1 file)
402 bytes,
text/plain
|
Details |
extracted from bug 758003 comment #17 by Shyam Mani [:fox2mike]:
> Hal,
>
> I'd like a new account or this account name changed before we go "live". It
> should just be github-sync@mozilla.com. Thoughts? Let's discuss on IRC
> before we go live.
Was discussed - not a go live blocker, so moved here.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [reit]
Reporter | ||
Comment 1•12 years ago
|
||
adding to tracker for b2g work - not sure how urgent this one is, but may be related to bug 791169
Blocks: 789350
Assignee | ||
Comment 2•12 years ago
|
||
Hal, do we want a new key for this? Or wrap this up with the other work to get new hardware etc?
Reporter | ||
Comment 3•12 years ago
|
||
New key would be better - let's sett on the account name so I can bake that into the public key.
Given various other changes in naming is "github-sync" hardcoded yet? If not, vcs-sync@m.c or vcs2vcs-sync@m.c seem more appropriate.
Let me know which you pick, and I'll gen the key
Flags: needinfo?(shyam)
Assignee | ||
Comment 4•12 years ago
|
||
I think vcs-sync makes more sense. We should probably eventually name the production hardware that too, when we move there.
Assignee: server-ops-devservices → shyam
Flags: needinfo?(shyam)
Reporter | ||
Comment 5•12 years ago
|
||
New ssh key for new account.
Note that we'll need to coordinate on cutover time for the account on git1.stage.dmz.scl3.mozilla.com
Assignee | ||
Comment 6•12 years ago
|
||
I've created the user, I want jabba to verify that the user was created correctly (uid etc) and we should be good to go.
Flags: needinfo?(jdow)
Assignee | ||
Comment 8•12 years ago
|
||
Awesome. Good to roll here.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•