I thought it might be interesting for folks to get an overview of the rate of change of RelEng infrastructure and perhaps a better idea of what RelEng work looks like. The following list was generated by looking at Release Engineering bugs that were marked as FIXED in the past week. Because it looks at only the “Release Engineering” product in Bugzilla it doesn’t represent everything that everyone in RelEng did, nor was all the work below done by people on the Release Engineering team, but I think it’s a good starting point!

• Emergency responses:
• disable updates for Windows, until the Windows nightly on the second rev finishes
• bouncer checks failing
• Regularly scheduled work:
• b2g merge day work
• Migrate mozilla-beta and comm-beta during 09-dec-2013 merge duty
• Kill mozilla-esr17 (2 versions after FF24 ships)
• Need automatic hsts preload list updates on esr24
• tracking bug for build and release of Firefox 24.2.0 ESR
• Disable Aurora 28 daily updates until merge to mozilla-aurora has stabilized
• tracking bug for build and release of Firefox and Fennec 26.0
• Remove old b2g branches: mozilla-b2g18_v1_0_1 and mozilla-b2g18_v1_0_0
• Disable Desktop Nightly builds and Windows 32 builds on b2g18 and b2g18_v1_1_0hd
• tracking bug for build and release of Firefox and Fennec 27.0b1
• General automation changes:
• Run Valgrind builds on every push
• Use mozinstall for installing b2g desktop builds in gaia-ui-tests script
• Trigger a retry for metro talos suites that fail to initialize metro browser
• Tests on the jetpack tree always test the most recent version of jetpack, not the push they are meant to test
• Servo build’s backup-rust step breaks on first-time slaves
• rootanalysis should be –enable-threadsafe
• Please schedule jit-tests on Try
• Please schedule cpp unittests on Try
• Collect and report output from Android x86 emulator
• Check connectivity to android emulators before and after tests
• blobber failed to upload minidump but didn’t give any useful debugging information
• Schedule b2g desktop mochitests on Cedar for OSX
• Run Valgrind builds on all mozilla-central-based trees (inbound, try, fx-team, etc)
• rootanalysis should be –enable-threadsafe
• Please schedule cpp unittests on all trunk trees and make them ride the trains
• OSX 10.6 talos is running on b2g-inbound
• npm mirror script fails occasionally
• Linkify and improve spidermonkey_build TinderboxPrint messages
• Marionette mozharness script should use proper xre.zip if running on osx
• Make it possible to perform editable installs in mozharness virtualenvs
• legacy vcs-sync process “silently” ignores missing repositories
• Schedule debug b2g emulator xpcshell tests on all trunk branches
• Hf builds need to output failures in a tbpl-recognizable way
• Build/test platform changes:
• Migrate w64-ix-slave day7 batch1 to rev2 image
• Manage slave secrets with puppet
• can’t ssh to some w64 rev2 machines
• Build/test machine requests:
• VM for RPM building
• loan jhammel a windows 8 slave for debugging
• Other:
• Drop talos-r4-lion from slave_health
• Upload an osx xre.zip to tooltool
• update.boot2gecko.org disk is filling up
• Unknown slaveclass for: Linux x86-64 mozilla-inbound valgrind on slave health
• slave health complaining about spot instances on try

http://hearsum.ca/blog/this-week-in-mozilla-releng-december-13th-2013/