Confirmed users
3,990
edits
CIDuty/Cronmail: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
These are cron jobs that release engineers get to receive. | |||
It informs of which actions to take (if any). | |||
= Cron <bhearsum@cruncher> /bin/bash /home/bhearsum/nonstarted-buildrequests.sh = | = Cron <bhearsum@cruncher> /bin/bash /home/bhearsum/nonstarted-buildrequests.sh = | ||
We noticed an issue this morning where some builds were scheduled but never actually started. We're still not sure what's causing it - it could be a freak event, could be related to https://bugzilla.mozilla.org/show_bug.cgi?id=893859 (though the evidence doesn't support that). It's not bad enough that trees have been closed, but it is something we need to keep an eye on. I've written a quick cronjob that will check for builds such as this every 15min. It's being sent to release@mozilla.com with "Cron <bhearsum@cruncher> /bin/bash /home/bhearsum/nonstarted-buildrequests.sh" as the subject. | We noticed an issue this morning where some builds were scheduled but never actually started. We're still not sure what's causing it - it could be a freak event, could be related to https://bugzilla.mozilla.org/show_bug.cgi?id=893859 (though the evidence doesn't support that). It's not bad enough that trees have been closed, but it is something we need to keep an eye on. I've written a quick cronjob that will check for builds such as this every 15min. It's being sent to release@mozilla.com with "Cron <bhearsum@cruncher> /bin/bash /home/bhearsum/nonstarted-buildrequests.sh" as the subject. | ||