QA/Execution/Web Testing/roles/buildmaster: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Initial creation of page)
 
(Alphabetize projects)
Line 32: Line 32:
==Projects==
==Projects==


===SUMO===
===amo===
* high priority
* fails: 1st krupa / 2nd mathieu agopian FRANCE / 3rd wil clouser
* file a bug
** https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org
 
===bidpom===
* towards low priority
* fail: john morrison [jrgm] if infrastructure related (time outs, buttons not loading, etc.); bob or davehunt are the ones to fix
* IRC: mozwebqa
* known bug file bug and also need info him; esp if you know who checked in the change who made it fail
** https://github.com/mozilla/bidpom/issues
 
===Marketplace===
* high priority
* fails: krupa 1st / 2nd david durst EST/ wil clouser 3rd
* IRC: #marketplace
* file a bug - if we know there's been a regression, if you can reproduce manually and you can correlate with what you see in automation, or if it's infrastructure related
** https://bugzilla.mozilla.org/enter_bug.cgi?product=Marketplace
 
===mozilla.org===
* medium-high priority
* fails: pmac/jgmize
* IRC: www
* file bug
** https://bugzilla.mozilla.org/enter_bug.cgi?product=www.mozilla.org
 
===Moztrap===
* lower priority
* fails: peterbe/camd
* IRC: moztrap
* file a bug
*** https://bugzilla.mozilla.org/enter_bug.cgi?component=MozTrap&product=Mozilla%20QA
 
===mozwebqa dashboard===
* low priority
* low priority
* fails: Mythmon, rdalal, r1cky [who is leaving SUMO]
* fail: bob
* contact: IRC sumodev
* IRC: mozwebqa
* known bug file bug and also need info him; esp if you know who checked in the change who made it fail
* https://github.com/mozilla/mozwebqa-dashboard/issues
** https://bugzilla.mozilla.org/enter_bug.cgi?product=support.mozilla.org


===One and Done===
===One and Done===
Line 51: Line 84:
* known bug file bug and also need info him; esp if you know who checked in the change who made it fail
* known bug file bug and also need info him; esp if you know who checked in the change who made it fail
** https://bugzilla.mozilla.org/enter_bug.cgi?product=Socorro
** https://bugzilla.mozilla.org/enter_bug.cgi?product=Socorro
===Sumo===
* low priority
* fails: Mythmon, rdalal, r1cky [who is leaving SUMO]
* contact: IRC sumodev
* known bug file bug and also need info him; esp if you know who checked in the change who made it fail
** https://bugzilla.mozilla.org/enter_bug.cgi?product=support.mozilla.org


===QMO===
===QMO===
Line 57: Line 97:
* could make a public job for contributors to workon or fix
* could make a public job for contributors to workon or fix
* https://bugzilla.mozilla.org/enter_bug.cgi?product=quality.mozilla.org
* https://bugzilla.mozilla.org/enter_bug.cgi?product=quality.mozilla.org
===mozwebqa dashboard===
* low priority
* fail: bob
* IRC: mozwebqa
* https://github.com/mozilla/mozwebqa-dashboard/issues
===bidpom===
* towards low priority
* fail: john morrison [jrgm] if infrastructure related (time outs, buttons not loading, etc.); bob or davehunt are the ones to fix
* IRC: mozwebqa
* known bug file bug and also need info him; esp if you know who checked in the change who made it fail
** https://github.com/mozilla/bidpom/issues
===moztrap===
* lower priority
* fails: peterbe/camd
* IRC: moztrap
* file a bug
*** https://bugzilla.mozilla.org/enter_bug.cgi?component=MozTrap&product=Mozilla%20QA
===mozilla.org===
* medium-high priority
* fails: pmac/jgmize
* IRC: www
* file bug
** https://bugzilla.mozilla.org/enter_bug.cgi?product=www.mozilla.org
===marketplace===
* high priority
* fails: krupa 1st / 2nd david durst EST/ wil clouser 3rd
* IRC: #marketplace
* file a bug - if we know there's been a regression, if you can reproduce manually and you can correlate with what you see in automation, or if it's infrastructure related
** https://bugzilla.mozilla.org/enter_bug.cgi?product=Marketplace
===amo===
* high priority
* fails: 1st krupa / 2nd mathieu agopian FRANCE / 3rd wil clouser
* file a bug
** https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org

Revision as of 22:49, 25 March 2015

Build Master

Role Definition

  • edit jenkins desc with your name as buildmaster
  • build master is point of contact for open issues/bugs
  • role includes filing bugs/issues, sending out emails, investigating issues
  • 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
  • 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

Support Tiers

Tier 1

  • Marketplace
  • AMO
  • Mozilla.org

Tier 2

  • SUMO
  • Socorro

Tier 3

  • BIDPOM
  • Affiliates
  • Mozillians
  • Moztrap
  • One and Done

Projects

amo

bidpom

  • towards low priority
  • fail: john morrison [jrgm] if infrastructure related (time outs, buttons not loading, etc.); bob or davehunt are the ones to fix
  • IRC: mozwebqa
  • known bug file bug and also need info him; esp if you know who checked in the change who made it fail

Marketplace

  • high priority
  • fails: krupa 1st / 2nd david durst EST/ wil clouser 3rd
  • IRC: #marketplace
  • file a bug - if we know there's been a regression, if you can reproduce manually and you can correlate with what you see in automation, or if it's infrastructure related

mozilla.org

Moztrap

mozwebqa dashboard

One and Done

Socorro

Sumo

QMO