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

adhoc, no more cot gpg
(add release+github, remove some older release aliases)
(adhoc, no more cot gpg)
 
Line 301: Line 301:
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?


=Mail to release+cot@mozilla.com=
=Mail to release+adhoc-signing@mozilla.com=
== Why we get them ==
== Why we get them ==
* gpg pubkey expiration monitoring ([https://bugzilla.mozilla.org/show_bug.cgi?id=1373986])
* adhoc repo release promotion


== What is sending them ==
== What is sending them ==
https://tools.taskcluster.net/hooks/project-releng/cot-gpg-keys%2Fexpiration
https://github.com/mozilla-releng/adhoc-signing relpro


== What to do when one is received ==
== What to do when one is received ==
* Alert the cot-gpg-keys contributors [https://github.com/mozilla-releng/cot-gpg-keys/graphs/contributors]
* Make sure we're expecting an adhoc signing operation


== How to silence or acknowledge this alert ==
== How to silence or acknowledge this alert ==
Confirmed users
4,971

edits