CIDuty/Meetings:2014-03-18
From MozillaWiki
< CIDuty
« previous week |
index |
next week »
< most recent |
upcoming >
Contents
Release Engineering Buildduty Meeting
- Date: Tuesdays
- Time: 1:00pm EST
- Room: ReleaseEngineering Vidyo room
- eeting notes: https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Meetings
Status of buildduty period
https://releng.etherpad.mozilla.org/buildduty <- last updated in Jan. Do we still use this? Is it useful?
Bugs filed
Things that could effect this/next week:
- https://bugzil.la/962190 - I requested some more improvements to the sanity check email
Owner wanted
https://bugzil.la/971861 - Fix graceful shutdown issue https://bugzil.la/984915 - Improve slave health for disabled slaves
Previous action items
Agenda
- Check the list of disabled slaves at the bottom of slave health
- sometimes they have been on loan for a long time and/or forgotten about
- RESOLUTION: filed https://bugzil.la/984915
- Please do not change slavealloc pool values unless you're connecting a machine to a staging master
- RESOLUTION: agreed
- (jlund) - I am seeing infra folks changing out component in loaning access bugs:
- Component: Infrastructure: OpenVPN → Mozilla VPN: ACL requests; Assignee: infra@infra-ops.bugs → vpn-acl@infra-ops.bugs
- should we be using this component from now on and if so, update our docs (bug create templates)?
- eg: https://bugzil.la/981074
- This was changed in HowTo page for loaners already! sweet!
- RESOLUTION: new process documented
- (jlund) if you agree with solution, have an alternative, or if you show me why I am wrong:
- ec2 loans are hard to catch when the loanee is finished. This is because:
- we don't have a tracking bugs for ec2 loan created instances (so we don't mark tracking bugs being blocked by loan bug and it doesn't show in buildduty report)
- we mark the loan bug as resolved and keep the assignee assigned (loanee)
- which makes it hidden from our loan tracking lists
- https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=releng-loan-requests-triage&sharer_id=30066&list_id=9659355
- https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=releng-loan-requests&sharer_id=30066&list_id=9659364
- NOTE: nagios looks at the first one for loan bugs that are open and no one is assigned
- which makes it hidden from our loan tracking lists
- solution: should we tell loanees to remove themselves from the bug and keep the bug open?
- RESOLUTION: we're are going be consistent with other slave types and filed the problem tracking bugs