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 15:28, 15 August 2014
, 15 August 2014add push to git.m.o failed email
(added link, fixed formatting) |
(add push to git.m.o failed email) |
||
| Line 23: | Line 23: | ||
|- | |- | ||
|Subject ||[vcs2vcs] alert_major_errors* || '''major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]] | |Subject ||[vcs2vcs] alert_major_errors* || '''major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]] | ||
|- | |||
|Subject ||[vcs2vcs]: git.m.o push failed: * || single occurrence related to git.m.o/releases/gecko.git '''if repeated, this is a major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]] | |||
|- | |- | ||
|Subject ||[vcs2vcs] process delays* || '''if repeated, this is a major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]] | |Subject ||[vcs2vcs] process delays* || '''if repeated, this is a major processing error''' make sure build duty and/or hwine know [[#vcs2vcs|details]] | ||
| Line 131: | Line 133: | ||
= vcs2vcs System= | = vcs2vcs System= | ||
== Why we get them == | == 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. | 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 and partners. | ||
== What is sending them == | == What is sending them == | ||
| Line 147: | Line 149: | ||
** NOTE: you may receive an additional email after the root cause is resolved. (The alert checks on the hour for problems in the prior hour.) | ** NOTE: you may receive an additional email after the root cause is resolved. (The alert checks on the hour for problems in the prior hour.) | ||
* if the subject | * if the subject containes "[vcs2vcs]: git.m.o push failed:", this is a (usually) transient problem with pushing gecko.git (the partner facing gecko repository) to either git.m.o or git staging. One or two is ignorable, more needs investigation, starting with the health of git.mozilla.org. (Note that the message is short, as this also pages hwine via sms, where brevity is nice.) | ||
* 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. | * 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. | ||