Release Engineering Buildduty Meeting

• Date: 2013-09-24
• Time: 1:30pm EDT
• Room: ReleaseEngineering Vidyo room
• Meeting notes: https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Meetings:2013-09-24

Status of buildduty period

https://releng.etherpad.mozilla.org/buildduty

Bugs filed

Previous action items

• Callek: schema for new foopy table in slavealloc db (+ join table)
  • Ongoing-carry
• armenzg: follow up on sheriffs
  • waiting on edmorley's reply
  • I did poke!
• coop: create query for problem tracking bugs "without" dep bugs
  • carryover
  • https://secure.pub.build.mozilla.org/builddata/reports/slave_health/buildduty_report.html
  • add links to sections
  • review logic
• coop: update nagios buildduty docs
  • carryover
  • follow-up with IT re: JSON formatting of nagios output
• armenzg: ping IT re: in-house master capacity for windows slaves
  • try to setup current in-house masters
• coop: add existing buildduty queries to wiki
  • reviewed existing queries with armenzg

Agenda

• slaveapi update
  • deployment
• Q4 goals?
  • slave pre-flight tasks
  • sheriffs able to self-serve machine reboots
    • slaveapi reboots from slave_health
  • report on disconnects as %age of overall builds
    • reduce %age or number of disconnects (stretch goal)
  • improve loaner process
    • start with AWS loaners using slaveapi
    • coordinate with Kim

List of current projects

• https://github.com/bhearsum/slaveapi/blob/master/TODO
• https://bugzilla.mozilla.org/show_bug.cgi?id=914764

Action items

• armenzg to put queries on buildduty page
• coop:
  • update nagios buildduty docs carryover
  • follow-up with IT re: JSON formatting of nagios output
  • add existing buildduty queries to wiki
  • reviewed existing queries with armenzg
  • automate buildduty_report generation
  • review buildduty report generation logic
  • all your actions items' are coop's
• bhearsum to add documentation at https://wiki.mozilla.org/ReleaseEngineering/Applications/SlaveAPI