Confirmed users
328
edits
AllHands2011/tbplPlanning: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
# monitor the results of a push (I also use the automated email for this) | # monitor the results of a push (I also use the automated email for this) | ||
# finish up the post-push workflow (updating bugs with commit messages) | # finish up the post-push workflow (updating bugs with commit messages) | ||
== Can I Push? == | |||
* Are there unstarred failures in recent builds? | |||
* What are they? Should I worry about them? | |||
** Intermittent oranges | |||
** A failure in one build might be fixed in a later build | |||
** Some infrastructure failures are not autodetected as such | |||
** For the rest, eyeball them briefly: | |||
*** does it look intermittent? | |||
*** does it look like it was caused by that same push? | |||
*** can I identify the culprit to harass them over IRC? (what channel?) | |||
*** has philor looked at it? is he already agitating over it? | |||
* Is the build infrastructure operating? (Are the expected set of jobs appearing?) | |||
* How far behind is the build infrastructure? (tbpl-at-a-glance more convincing than magically derived "expected wait time") | |||
== Prep for a Push == | |||
* Star anything not yet starred | |||
* Wait until scary jobs go through | |||
== Monitoring a Push == | |||
* Watch for new failures on preceding pushes | |||
* Watch for failures on my push | |||
** Triage the failures | |||
** Trigger a backout | |||