Confirmed users
1,504
edits
QA/Execution/Web Testing/roles/buildmaster: Difference between revisions
Jump to navigation
Jump to search
QA/Execution/Web Testing/roles/buildmaster (view source)
Revision as of 21:12, 12 June 2015
, 12 June 2015→Definition
m (→Projects) |
|||
| Line 13: | Line 13: | ||
* buildmaster role last 2 weeks | * buildmaster role last 2 weeks | ||
* edit jenkins desc with your name as buildmaster | * edit jenkins desc with your name as buildmaster | ||
* check builds at least once per day (there are several methods for doing this: view the web dashboard, subscribe to RSS feeds, read e-mail alerts, watch IRC notifications. We could consider others using Jenkins plugins) | |||
** investigate failures | |||
** If it is a locator issue, if you have a question, if you wonder if the test is still valid or important then file a GitHub issue | |||
** File bugs on projects based on info below, then contact the noted team members | |||
* File Git Issues for test failures that require a test update. | |||
** Label issue "test failure" with a priority | |||
** Xfail the failing test to get the build green | |||
* buildmaster is point of contact for open issues/bugs | * buildmaster is point of contact for open issues/bugs | ||
* role includes filing bugs/issues, sending out emails, investigating issues | * role includes filing bugs/issues, sending out emails, investigating issues | ||
* does NOT include escalation paths, prioritizing fixes, following up with other teams | * does NOT include escalation paths, prioritizing fixes, following up with other teams | ||
* send daily email with list of generally prioritized github issues to be fixed, blocking bugs that were filed | * send daily email with list of generally prioritized github issues to be fixed, blocking bugs that were filed | ||
=Known Issues= | =Known Issues= | ||