Confirmed users
1,364
edits
ReleaseEngineering/How To/Process release email: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Process release email (view source)
Revision as of 16:55, 4 November 2012
, 4 November 2012added more vcs2vcs info
(add release+vcs2vcs email) |
(added more vcs2vcs info) |
||
| Line 20: | Line 20: | ||
|- | |- | ||
|Subject ||Try submission *||to: autolanduser@mozilla.com | |Subject ||Try submission *||to: autolanduser@mozilla.com | ||
|- | |||
|Subject ||[vcs2vcs] alert_major_errors* || '''major processing error''' make sure build duty and/or hwine know [[#vcs2vcs details]] | |||
|- | |- | ||
|To || release+aws@mozilla.com || AWS admin email (contact catlee for now) | |To || release+aws@mozilla.com || AWS admin email (contact catlee for now) | ||
| Line 25: | Line 27: | ||
|To || release+bitbucket@mozilla.com || Mozilla Bitbucket Admin email (contact hwine for now) | |To || release+bitbucket@mozilla.com || Mozilla Bitbucket Admin email (contact hwine for now) | ||
|- | |- | ||
|To || release+vcs2vcs@mozilla.com || Output from vcs2vcs hg<->git conversion ( | |To || release+vcs2vcs@mozilla.com || Output from vcs2vcs hg<->git conversion ([[#vcs2vcs details]]) | ||
|} | |} | ||
<br /> | |||
__TOC__ | |||
=briar-patch idle kittens reporting= | =briar-patch idle kittens reporting= | ||
| Line 110: | Line 116: | ||
== How to best filter these emails == | == How to best filter these emails == | ||
Since these are adhoc, you'll need adhoc filters. It would be nice if folks used a common prefix on subjects, such as "<tt><nowiki>[releng metrics]</nowiki></tt>". | Since these are adhoc, you'll need adhoc filters. It would be nice if folks used a common prefix on subjects, such as "<tt><nowiki>[releng metrics]</nowiki></tt>". | ||
<div id="vcs2vcs"> </div> | |||
=vcs2vcs System= | |||
== Why we get them == | |||
These emails are the interim notification for vcs2vcs system, and indicate an error that must be addressed. The b2g project is dependent upon parts of the vcs2vcs system, as are other developers. | |||
== What is sending them == | |||
All emails are sent (perhaps indirectly) by a script from [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/ vcs2vcs tools]. The hosts sending the email will be one of the ones listed in [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/file/default/status the configs]. Full details of how each script is run, including trouble shooting tips, are in the [http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/file/default/docs docs] (a formatted copy ''may'' be online [http://people.mozilla.com/~hwine/tmp/hg-git/ here]). | |||
== What to do when one is recieved == | |||
* if the subject contains "[vcs2vcs] alert_major_errors alert", this is a major problem - one or more repositories are no longer being updated. The email contents will give specific errors. Consult the docs for guidance and/or contact hwine. | |||
* if the subject is something else, this is likely unexpected output from a cron job. Judge the severity and escalate to hwine appropriately. File a bug to get better diagnosis of this error condition in the future. | |||
== How to silence or acknowledge this alert == | |||
Resolving the root cause will stop the emails. | |||
== Future plans == | |||
The system will eventually be transitioned to IT for operations. Specific email will be converted to nagios alerts before then. | |||
== How to best filter these emails == | |||
All of these emails are sent to the addresses of the form: <tt>release+vcs2vcs*@mozilla.com</tt>. Common sub addresses are: | |||
; release+vcs2vcs : mail that will a specifics in the Subject line. | |||
; release+vcs2vcs+forward : mail to vcs2vcs user, forwarded via <tt>~/.forward</tt> file. | |||
<hr /> | <hr /> | ||
<small> | |||
=Sample= | =Sample= | ||
== Why we get them == | == Why we get them == | ||
| Line 132: | Line 161: | ||
== How to best filter these emails == | == How to best filter these emails == | ||
provide insight on how to filter these emails. Is there a distinguishing header? Is it always from a specifc host, or family of hosts? Is there a distinctive subject? | provide insight on how to filter these emails. Is there a distinguishing header? Is it always from a specifc host, or family of hosts? Is there a distinctive subject? | ||
</small> | |||