CloudServices/QA Team/Meetings/2016-03-29

From MozillaWiki
Jump to: navigation, search

Meeting details

The Cloud Services QA Team meets weekly, Tuesdays at 11am Pacific time.

List of previous meetings

Lead / Scribe

  • Lead:
  • Scribe:
    • Scribe is responsible for:
      • adding the action items and takeaways to the current meeting's minutes
      • creating the agenda for the next meeting and carrying the action items and takeaways over to it
      • sending out a notice of the availability of that agenda along with the meeting invite
      • completing all of the above by the end of the week during which the meeting occurred

Last week's action items

Read-only

Discussion items

  • Rotate meeting roles: agenda prep, notetaking/scribing, (optional) timekeeping. Stuart, do you want to lead all of these, or rotate?

Status updates

Announcements:

  • Mark goals done in Workday for Q1.
  • Intern projects? -- talk to Stuart today
  • Continuing emphasis on automation
  • Flakiness of existing tests -- emphasis in Q2
  • A couple of new projects: Content Signing, Telemetry.
  • Taipei -- automation folks going to RelEng, manual folks maybe take some self-contained projects
    • If we have such projects, they might go to taipei
  • Sumo and MDN cut-over to Taipei -- Ben Sternthal's group may outsource this go a Python consulting firm instead.

Matt:

  • New and different workflows!
  • Stabilizing Socorro tests
  • MDN -- working with Stuart (and possibly Ben) to see about QA story
  • Meeting with Karl, Stuart, Rebecca about Q1 deliverables

Peter:

  • Activity Streama nd Test Pilot moving along
  • React and CORS headers causing problems on loads-web
  • Push dashboards -- travis

Richard:

  • Autopush deploy tomorrow -- how do we test this today?
  • Destroy Autopush in SF last week -- new scenarios in ap-loadtester
  • Crypto
  • Benson at al -- cloudbees
  • real load test for autopush needed soon

Chris:

  • Toronto office!
  • Met with Ben Hearsum -- balrog -- dockerized!
  • Normandy -- automated tests running. More Dockerization with Mike Cooper.
  • loop-server working on staging? plugin last week -- went out without QA?
  • pull request to Richard for url checks for loop-standalone
  • staging test at 4pm EDT today
  • off Thursday and Friday this week
  • loop-standalone prod push tomorrow

Karl:

  • Huge thanks to Peter/Richard for helping while Cynthia was here
  • peter was quite hospitable last week, in contrast to the usual
  • sync load testing with bobm (may not get started today), but meeting w/ bob every week for rest of quarter
  • re-architecting sync to avoid corruption and resizing sync clusters.
  • migrating sync clusters (non-trivial) and will take up KT's brain-space
  • TPS running from Jenkins (at the push of a button), but no reporting [yet]. Will report directly into Bugzilla bugs in the future. KT to talk to SPhilp.
  • Talking w/ Mbrandt about one-and-done.
  • Talking w/ chartjes about using one-and-done for on-boarding purposes.
  • working on Telemetry stuff, but isn't strongly defined yet.
  • Services-OPS having a work week in MTV. KT to talk to OPs guy about ____.
  • Thom is new dev hire on sync.
  • KT is travelling on Wed and sporadic Thu/Fri NEXT week (will put in calendar).

Stephen:

  • NetSparker! authenticated results amo-staging vs ZAP
  • latest version of Selenium -- 2.52 last week, now on current Firefox, one version of Selenium behind -- update this week
  • buildmaster -- painful as an IC -- confer with Stuart about pipelines and understand the key categories of failures
  • git and python classes -- making progress
  • snippets moving to AWS -- WebOps hiccups -- working with Engagement - we're always watching

John Dorlus:

  • This week is nuts. Closing today, jury duty on Thursday.

Goals Check-in - 1st and 3rd meetings, monthly

Upcoming Events

Blog Ideas

Lightning talks

Project status / goals for next week (keep it brief)

  • High-priority/supported projects:
  • Available for ownership:
    • Webmaker
    • REMO/Mozilla Reps
    • Wiki

CI updates

If you've worked on Jenkins or Selenium Grid in the last week, add the necessary info in the Wiki

Community update

Time off / Out-of-office

Action items

Next Meeting

  • Next owner / scribe:
  • Next week's meeting notes: