470
edits
ReleaseEngineering/How To/Process release email: Difference between revisions
ReleaseEngineering/How To/Process release email (view source)
Revision as of 16:57, 7 March 2012
, 7 March 2012no edit summary
No edit summary |
mNo edit summary |
||
| Line 8: | Line 8: | ||
!Field !! Wildcard !! Further Notes | !Field !! Wildcard !! Further Notes | ||
|- | |||
|Subject || idle kittens report || [[#briar-patch idle kittens reporting]] | |||
|- | |- | ||
|Subject || Humpty Dumpty Error * || [[#Puppet failing too many times on a slave]] | |Subject || Humpty Dumpty Error * || [[#Puppet failing too many times on a slave]] | ||
| Line 17: | Line 19: | ||
|Subject ||Try submission *||to: autolanduser@mozilla.com | |Subject ||Try submission *||to: autolanduser@mozilla.com | ||
|} | |} | ||
=briar-patch idle kittens reporting= | |||
== Why we get them == | |||
Email report outlining the status of any host that has been flagged as "idle" | |||
== What is sending them == | |||
A cron job that is running the kittenreaper.py task with the following parameters | |||
python kittenreaper.py -w 1 -e | |||
It pulls the list of hosts to check from http://build.mozilla.org/builds/slaves_needing_reboot.txt | |||
== What to do when one is recieved == | |||
not sure yet, unless your buildduty - then you should be watching it | |||
== Future plans == | |||
This will be replaced by the briar-patch dashboard | |||
== How to best filter these emails == | |||
Filtering can be done by matching the subject line which will not change | |||
=Puppet Log Monitoring= | =Puppet Log Monitoring= | ||