ReleaseEngineering/Day 1 Checklist: Difference between revisions
ChrisCooper (talk | contribs) (Created page with "__TOC__ Welcome to Release Engineering! This page is meant to get new hires, interns, or interested community members up to speed with the right software, configurations, a...") |
ChrisCooper (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
Welcome to Release Engineering! | Welcome to Release Engineering! | ||
This page is meant to get new hires, interns, or interested community members up to speed with the right software, configurations, and | This page is meant to get new hires, interns, or interested community members up to speed with the right software, configurations, and communication channels to contribute effectively to the release engineering pipeline. | ||
= Video Introductions = | = Video Introductions = | ||
| Line 30: | Line 30: | ||
These are available as [news://news.mozilla.org newsgroups], google groups, and [https://lists.mozilla.org/listinfo Mailman lists] | These are available as [news://news.mozilla.org newsgroups], google groups, and [https://lists.mozilla.org/listinfo Mailman lists] | ||
= Email Filtering = | |||
With all that new email, you will want to set up some filters in Gmail (https://mail.google.com/mail/u/0/#settings/filters) to filter some of the higher-volume automated mail into a folder. You may eventually want to handle this information, but on day one hundreds of nagios notifications are not going to be educational. | |||
Here is [http://people.mozilla.org/~coop/mozillaMailFilters.xml an imperfect set of Gmail filters] that you can import to get you started. | |||
A list of new (and some older) automated emails are indexed by subject, along with relevant actions, [https://wiki.mozilla.org/ReleaseEngineering/How_To/Process_release_email here]. | |||
If you are going to working on puppet, you should also look at this page: [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Read_Releng-Shared_Emails] | |||
Revision as of 17:07, 30 April 2015
Welcome to Release Engineering!
This page is meant to get new hires, interns, or interested community members up to speed with the right software, configurations, and communication channels to contribute effectively to the release engineering pipeline.
Video Introductions
- Release Engineering as a Force Multiplier by John O'Duinn (former director) about how Mozilla Release Engineering handles our business and how we work to improve each and every day.
- This crowd-sourced video list contains other videos about various aspects of working at Mozilla, including important information such as how to operate the espresso machine.
Development Best Practices
- Read and keep up to date with: Development Best Practices
- Read and keep up to date with: http://moz-releng-docs.readthedocs.org/en/latest/
- Please fix any issues you find: https://github.com/mozilla/build-relengdocs As someone new to the project, your fresh perspective helps shine a light on missing information or assumptions we take for granted.
Mailing list subscriptions
- release@mozilla.com - this should happen automatically as a new hire/intern.
- Send a test message to release@m.c to verify that your address has been added/subscribed. Open a ticket in ServiceNow if it isn't working.
- WARNING: release@m.c can contain security-sensitive information. Do not automatically forward your email to a system that is not under Mozilla's control.
You'll need to manually subscribe to
- release-engineering public mailing list
- release-drivers mailing list
- mozilla.dev.planning
- mozilla.dev.tree-management
These are available as newsgroups, google groups, and Mailman lists
Email Filtering
With all that new email, you will want to set up some filters in Gmail (https://mail.google.com/mail/u/0/#settings/filters) to filter some of the higher-volume automated mail into a folder. You may eventually want to handle this information, but on day one hundreds of nagios notifications are not going to be educational.
Here is an imperfect set of Gmail filters that you can import to get you started.
A list of new (and some older) automated emails are indexed by subject, along with relevant actions, here.
If you are going to working on puppet, you should also look at this page: [1]