canmove, Confirmed users
2,850
edits
CIDuty: Difference between revisions
Jump to navigation
Jump to search
→Semi-Daily
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) |
||
| Line 53: | Line 53: | ||
** Run [[ReleaseEngineering/Buildduty/Reconfigs|reconfigs]] (every day or two days) for other release engineers. Reconfigs are automated now, so this is usually just a matter of merging the relevant repositories to production. | ** Run [[ReleaseEngineering/Buildduty/Reconfigs|reconfigs]] (every day or two days) for other release engineers. Reconfigs are automated now, so this is usually just a matter of merging the relevant repositories to production. | ||
* '''Review logs in papertrail''' | * '''Review logs in papertrail''' | ||
** We have SNS alerts for most known issues. The alerts will appear in the #buildduty IRC channel. Buildduty should log into papertrail a few times a week (M/W/F) to check for new issues that are *not* covered by alerts. New alerts should be setup for these issues. | ** We have SNS alerts for most known issues in papertrail. The alerts will appear in the #buildduty IRC channel. Buildduty should log into [https://papertrailapp.com/dashboard papertrail] a few times a week (M/W/F) to check for new issues that are *not* covered by alerts. New alerts should be setup for these issues. | ||
=== Weekly === | === Weekly === | ||