CIDuty/Meetings:2014-02-18
< CIDuty
Jump to navigation
Jump to search
« previous week |
index |
next week »
< most recent |
upcoming >
Release Engineering Buildduty Meeting
- Date: Tuesdays
- Time: 1:00pm EST
- Room: ReleaseEngineering Vidyo room
- Meeting notes: https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Meetings:2014-02-18
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.la980890 - Integration Trees closed, high number/time backlog of pending jobs
- https://bugzil.la978928 - Reconfigs should be automatic, and scheduled via a cron job
- https://bugzil.la978971 - Spot bidding should be able to filter out AZs with bad conditions
Previous action items
FYI
- https://bugzil.la/962190 - I requested some more improvements to the sanity check email
Agenda
- scl3 <-> usw2 link - https://bugzilla.mozilla.org/show_bug.cgi?id=975438
- Bug 971861 - slaveapi's shutdown_buildslave action doesn't cope well with a machine that isn't connected to buildbot
- required manual reboots due to this bug
- 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
- doesn't require a meeting: 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
- I don't need to bring this up in mtg 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?