Confirmed users
2,204
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 17:29, 23 April 2015
, 23 April 2015no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
= | =Introduction= | ||
Create a set of guidelines for investigating failures in our public Jenkins instance. This would be used by whoever is monitoring for failures, but would also be valuable for community who want to dive in. It should include how to identify failures, how to determine if they're already known, how to replicate them locally, how to determine if they're application bugs or test bugs, where to raise them, who to notify, and even how to fix them (if they're test failures) and submit pull requests. This could form part of a boot camp similar to other teams. -- from our 2015, [https://etherpad.mozilla.org/webqa-goals-2015-q2 Q2 goals brainstorm]. | Create a set of guidelines for investigating failures in our public Jenkins instance. This would be used by whoever is monitoring for failures, but would also be valuable for community who want to dive in. It should include how to identify failures, how to determine if they're already known, how to replicate them locally, how to determine if they're application bugs or test bugs, where to raise them, who to notify, and even how to fix them (if they're test failures) and submit pull requests. This could form part of a boot camp similar to other teams. -- from our 2015, [https://etherpad.mozilla.org/webqa-goals-2015-q2 Q2 goals brainstorm]. | ||
=Open Questions= | |||
* In the interests of reducing complexity, do we need tiers? Are we anticipating that there will be so many failures that some need prioritizing over others? | * In the interests of reducing complexity, do we need tiers? Are we anticipating that there will be so many failures that some need prioritizing over others? | ||
* On the topic of sending daily emails - I think this would be extra work and considered noise by most recipients. It could be done via a whiteboard entry and Bugzilla whines. | * On the topic of sending daily emails - I think this would be extra work and considered noise by most recipients. It could be done via a whiteboard entry and Bugzilla whines. | ||
* On the topic of checking builds once a 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. | * On the topic of checking builds once a 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. | ||
== | =Rotation= | ||
{{WebQABuildMasterRotation}} | |||
= | =Definition= | ||
* 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 | ||
| Line 24: | Line 22: | ||
** File bugs on projects based on info below, then contact the noted team members | ** File bugs on projects based on info below, then contact the noted team members | ||
=Support Tiers= | |||
===Tier 1=== | ===Tier 1=== | ||
| Line 44: | Line 42: | ||
* Mozillians | * Mozillians | ||
=Projects= | |||
===amo=== | ===amo=== | ||
| Line 116: | Line 114: | ||
* https://bugzilla.mozilla.org/enter_bug.cgi?product=quality.mozilla.org | * https://bugzilla.mozilla.org/enter_bug.cgi?product=quality.mozilla.org | ||
=FAQ= | |||
===Who do I contact if the issue is related to Persona?=== | ===Who do I contact if the issue is related to Persona?=== | ||