Confirmed users
4,293
edits
ReleaseEngineering/Day 1 Checklist: Difference between revisions
Assorted updating (moar ircloud links, slack, move vidyo up, ssh key generation, remove people ahead of EOL
(→Bugzilla: update admin users) |
(Assorted updating (moar ircloud links, slack, move vidyo up, ssh key generation, remove people ahead of EOL) |
||
| Line 70: | Line 70: | ||
== Filing bugs against Release Engineering == | == Filing bugs against Release Engineering == | ||
The product to use is, unsurprisingly, "Release Engineering." There are multiple possible components under that product, so take your best guess or ask for guidance in IRC. | The product to use is, unsurprisingly, "Release Engineering." There are multiple possible components under that product, so take your best guess or ask for guidance in IRC. | ||
== Vidyo Services == | |||
Our primary two way video meeting platform is Vidyo. Basic usage instructions are [https://mana.mozilla.org/wiki/display/SD/Vidyo+Desktop+3 here]. Especially if you are running linux, it is highly recommended that you install the client and make test calls prior to any meeting. Many of our team meetings are held in the '''ReleaseEngineering''' room. | |||
* ''Pro tip: many folks have found the mobile client useful to have preinstalled as a backup device.'' | |||
* If you're going to record a meeting, practice first. (Instructions are linked from [https://mana.mozilla.org/wiki/display/SD/Vidyo+Desktop+3 mana page].) | |||
* Ask team members for details on recording in the '''ReleaseEngineering''' room. | |||
== LDAP, SSH, VPN == | == LDAP, SSH, VPN == | ||
'''''Warning for people who already have an LDAP account:''''' '''Change your password.''' Otherwise, adding you to the releng group may lock your account without further notice. There is a stronger password policy in releng: users must change their password every 3 months. If you don't change your password, the only symptom will be that one day or another (already observed after 8 days), your regular password won't work anymore. If this happens to you, contact people in #servicedesk, they will be able to reset your password. | '''''Warning for people who already have an LDAP account:''''' '''Change your password.''' Otherwise, adding you to the releng group may lock your account without further notice. | ||
'''''Note:There is a stronger password policy in releng: users must change their password every 3 months.''''' If you don't change your password, the only symptom will be that one day or another (already observed after 8 days), your regular password won't work anymore. If this happens to you, contact people in #servicedesk, they will be able to reset your password. | |||
This is mostly applicable only to employees and interns, although it *is* possible for other contributors to acquire some limited LDAP access. Speak to someone you work with on the releng team if you would like to investigate this. | This is mostly applicable only to employees and interns, although it *is* possible for other contributors to acquire some limited LDAP access. Speak to someone you work with on the releng team if you would like to investigate this. | ||
SSH keys are used for access to most machines, and some of them are stored in your LDAP record: | SSH keys are used for access to most machines, and some of them are stored in your LDAP record: | ||
* Generate a key for Mozilla based on the [https://wiki.mozilla.org/Security/Guidelines/OpenSSH#OpenSSH_client Security's recommendations]. If you are connecting to buildbot masters and slaves you will need to use the Intermediate ssh config. | |||
* Add your SSH public key to your LDAP account, at https://login.mozilla.com/ | * Add your SSH public key to your LDAP account, at https://login.mozilla.com/ | ||
| Line 110: | Line 119: | ||
cn=vpn_relengwiki,ou=groups,dc=mozilla | cn=vpn_relengwiki,ou=groups,dc=mozilla | ||
cn=vpn_tooltooleditor,ou=groups,dc=mozilla | cn=vpn_tooltooleditor,ou=groups,dc=mozilla | ||
=== Build Machines === | === Build Machines === | ||
| Line 130: | Line 134: | ||
# Ask for a reviewer. Your mentor/manager are good options here. | # Ask for a reviewer. Your mentor/manager are good options here. | ||
If you need an account on cruncher (shared releng machine) | If you need an account on cruncher-aws (shared releng machine) ask catlee, and send him your SSH public key. (If you aren't sure you need the account, you probably do not for now.) | ||
=== SSH Config === | === SSH Config === | ||
You'll want to update your ~/.ssh/config accordingly: | You'll want to update your ~/.ssh/config accordingly: | ||
<pre class="_fck_mw_lspace">Host hg | <pre class="_fck_mw_lspace">Host hg.mozilla.org | ||
User <short-ldap-name-here>@mozilla.com | User <short-ldap-name-here>@mozilla.com | ||
Compression yes | Compression yes | ||
| Line 149: | Line 153: | ||
User cltbld | User cltbld | ||
ServerAliveInterval 300</pre> | ServerAliveInterval 300</pre> | ||
You can add an <tt>IdentityFile ~/.ssh/<filename></tt> line to those blocks to specify separate keys for different systems (eg Github). | |||
== Mercurial (hg) == | == Mercurial (hg) == | ||
| Line 162: | Line 168: | ||
* Level 1 access allows you to use the [[ReleaseEngineering/TryServer|Try Server]] and setup user repos. As a new contributor, you should request this on day one. | * Level 1 access allows you to use the [[ReleaseEngineering/TryServer|Try Server]] and setup user repos. As a new contributor, you should request this on day one. | ||
* Level 2 access is required to land code in the build and project repos. Once you have a proven track record of successful patches, you can ask your manager/mentor to vouch for your Level 2 access. Your manager/mentor can also land patches for you until you receive Level 2 access. | * Level 2 access is required to land code in the build and project repos. Once you have a proven track record of successful patches, you can ask your manager/mentor to vouch for your Level 2 access. Your manager/mentor can also land patches for you until you receive Level 2 access. | ||
* Level 3 access is required to land code | * Level 3 access is required to land code in [https://hg.mozilla.org/mozilla-central mozilla-central] and its derived integration & release branches. At some point in your Mozilla contribution story, you may need Level 3 access but many contributors never do. Talk to your manager/mentor if you think you need this access. You should already have Level 2 access when you request Level 3. | ||
You need to file an IT bug to get hg commit access. Follow the instructions for [https://www.mozilla.org/en-US/about/governance/policies/commit/ Becoming a Mozilla Committer], and for Level 2, specify you need access to (at least) hg.mozilla.org/build/* (Product/Component: mozilla.org/Repository Account Requests). | You need to file an IT bug to get hg commit access. Follow the instructions for [https://www.mozilla.org/en-US/about/governance/policies/commit/ Becoming a Mozilla Committer], and for Level 2, specify you need access to (at least) hg.mozilla.org/build/* (Product/Component: mozilla.org/Repository Account Requests). | ||
| Line 168: | Line 174: | ||
== Git & Github == | == Git & Github == | ||
There are git mirrors of many popular Mozilla repositories. One of the Mozilla github admins (catlee, | There are git mirrors of many popular Mozilla repositories. One of the Mozilla github admins (catlee, kmoir, jlund) can add you to the following GitHub groups: | ||
* [https://github.com/mozilla-releng Mozilla-Releng organization] | * [https://github.com/mozilla-releng Mozilla-Releng organization] | ||
* [https://github.com/orgs/mozilla/teams/releng Releng team within the Mozilla organization] | * [https://github.com/orgs/mozilla/teams/releng Releng team within the Mozilla organization] | ||
| Line 188: | Line 194: | ||
== IRC == | == IRC == | ||
The majority of day-to-day communication in releng happens on IRC: | The majority of day-to-day communication in releng happens on IRC, and many people use the locally-hosted irccloud instance. Servicedesk has some great [https://mana.mozilla.org/wiki/display/SD/Internet+Relay+Chat+-+IRC getting started tips] for IRC. | ||
If you run a traditional IRC client: | |||
* https://wiki.mozilla.org/IRC irc://irc.mozilla.org | * https://wiki.mozilla.org/IRC irc://irc.mozilla.org | ||
* irc.mozilla.org:6697 #mozbuild (use SSL, ask for the channel key; your nick needs to be registered) | * irc.mozilla.org:6697 #mozbuild (use SSL, ask for the channel key; your nick needs to be registered) | ||
| Line 196: | Line 204: | ||
* irc.mozilla.org #releng | * irc.mozilla.org #releng | ||
** public channel for discussion with | ** public channel for discussion with sheriffs, and continuous integration bot | ||
* keywords to hilite on: | * keywords to hilite on: | ||
** "!squirrel" is "I need eyes on this now" keyword in #mozbuild & #releng- please set your client to alert on it. | ** "!squirrel" is "I need eyes on this now" keyword in #mozbuild & #releng- please set your client to alert on it. | ||
| Line 203: | Line 211: | ||
* also useful to join | * also useful to join | ||
** #developers, #airmozilla, #sf, #mobile, #planning, #release-drivers, #ateam, | ** #developers, #airmozilla, #sf, #mobile, #planning, #release-drivers, #ateam, | ||
** # | ** #moco access_key is [https://mana.mozilla.org/wiki/display/AVSE/MoCo+Vidyo+Room+and+%23moco+IRC+Channel+Security on mana] | ||
** #firebot for hiliting when you're mentioned in a bug, review request, etc. | ** #firebot for hiliting when you're mentioned in a bug, review request, etc. | ||
* http://chatzilla.hacksrus.com/faq/#connect | * http://chatzilla.hacksrus.com/faq/#connect | ||
Some folks run a BNC (an IRC bouncer) (e.g. znc) and/or <tt>irssi</tt> under screen to get continuous view of traffic. Ask around. (some [https://mana.mozilla.org/wiki/display/SYSADMIN/IRC+use+within+IT#IRCusewithinIT-irssi good irssi notes]). | |||
See [[#pastebin|below]] for a local pastebin install, so you don't paste huge amounts in channel. | See [[#pastebin|below]] for a local pastebin install, so you don't paste huge amounts in channel (irccloud handles this internally). | ||
IT now also provides a hosted [https://mana.mozilla.org/wiki/display/SD/IRCCloud+Account+Setup IRCCloud cloud] instance you can partake of. | IT now also provides a hosted [https://mana.mozilla.org/wiki/display/SD/IRCCloud+Account+Setup IRCCloud cloud] instance you can partake of. | ||
| Line 220: | Line 227: | ||
*# Click the "Rejoin" button | *# Click the "Rejoin" button | ||
*# Paste the password into the text box. | *# Paste the password into the text box. | ||
== Slack == | |||
Some parts of Mozilla prefer Slack to IRC, more info on [https://mana.mozilla.org/wiki/display/CCT/Slack mana]. | |||
== Wiki == | == Wiki == | ||
| Line 247: | Line 257: | ||
== Mana == | == Mana == | ||
Some internal Mozilla systems (IT, HR) are documented on [https://mana.mozilla.org mana]. File a [https://mozilla.service-now.com/ ServiceNow] ticket if you don't have access when you start. | Some internal Mozilla systems (IT, HR) are documented on [https://mana.mozilla.org mana]. File a [https://mozilla.service-now.com/ ServiceNow] ticket if you don't have access when you start. | ||
== Other Resources == | == Other Resources == | ||