QA/Execution/Web Testing/roles/buildmaster

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

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

One and Done

• low priority
• bob
• https://bugzilla.mozilla.org/enter_bug.cgi?component=One%20and%20Done&product=Mozilla%20QA

Socorro

• low priority, no rush
• tests will be pared down to match less upcoming features
• fails: mbrandt and rhelmer,
• contact: IRC breakpad
• 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

QMO

• low priority
• tests not in jenkins
• could make a public job for contributors to workon or fix
• 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