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 18:20, 14 November 2012
, 14 November 2012added "terminated"
m (correct link syntax) |
(added "terminated") |
||
| Line 127: | Line 127: | ||
== What to do when one is recieved == | == 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 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 contains "TERMINATED", this is a major problem with the update of gecko.git (interim version). Contact (page) hwine <small>(note: this comes from the interim script "keep_clean_room_updated" running in vcs2vcs@github-sync2.dmz.scl3:/opt/vcs2vcs/b2g/wip/" as of 2012-11-10)</small> | |||
* 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. | ||