ReleaseEngineering/How To/Process release email: Difference between revisions

update on email processing for vcs-sync system
m (spelling nazi woz here)
(update on email processing for vcs-sync system)
Line 24: Line 24:
|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] process delays* || '''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]]
|-
|-
|To      || release+aws@mozilla.com || AWS admin email (contact catlee for now), both important & marketing
|To      || release+aws@mozilla.com || AWS admin email (contact catlee for now), both important & marketing
Line 129: Line 129:


== What to do when one is received ==
== What to do when one is received ==
* if the subject contains "[vcs2vcs] process delays", this is a service outage - one or more repositories are no longer being updated. The email contents will give specific errors. Consult the trouble shooting section of the docs (above) for guidance and/or PAGE hwine.  
* if the subject contains "[vcs2vcs] AUTOFIX process delays", then look for another email within a few minutes and proceed as follows:
** The most common cause of this is "socket hang" which is a quick fix. Please add to {{bug|829025}} if you fix, or block that with a new bug.
** if a second email from the same host follows almost immediately with a subject of "[vcs2vcs] process delays", then the AUTOFIX failed, which is an unexpected condition. Page hwine.
** if no followup email is received, the AUTOFIX worked. Log in {{bug|829025}} & delete (or just delete and leave for hwine to log).
* if the subject contains "[vcs2vcs] process delays" '''''and''''' is repeated every 20 minutes, this is a service outage - one or more repositories are no longer being updated. The email contents will give specific errors. Consult the trouble shooting section of the docs (above) for guidance and/or PAGE hwine.  
** Unfortunately, there appear to be a few race conditions between scripts, so a single occurrence of the email may be a false positive. ({{bug|839595}} filed to track this.)


* 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 trouble shooting section of the docs (above) for guidance and/or contact hwine.  
* 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 trouble shooting section of the docs (above) for guidance and/or contact hwine.  
Confirmed users
1,364

edits