lsblakk: All Posts

Done:

  • landed and reconfig'd for addition of 22 new talos-r3 slaves
  • filed dep bugs for test-master02
  • met with catlee and set up next steps for try server
  • met with myk, clint, brian, joduinn and blocked out next steps for jetpack-sdk test suite & poller
  • buildduty tasks

Next:

  • pull from hg via ssh for private repo
  • upload to secure ftp for private repo
  • get those 22 talos-r3 slaves attached to masters
  • test-master02 configs checked in, all three test masters reconfig'd so it will start taking on jobs
  • turn off talos for try by default

Done:

  • Summit.

Next:

  • get new talos/build slaves online
  • buildduty
  • shadow-central into staging
  • meeting re: jetpack-sdk unittest suite
  • meet with catlee to discuss Q3 tryserver goals

Done:

  • Jaegermonkey branch live in production
  • mozilla-2.0 branch live in production (still needs release abilities on 0.8.0)
  • staging private repo started
  • added 5 more linux64 slaves to try pool

Next:

  • work on try unittests going to talos was almost done but then got backed out due to load issues on test-master01, not sure what next step is there
  • working on private repo
  • developing jetpack-sdk poller to trigger talos jetpack unittest suite
  • cleaning up some other small bugs

Coordination:

  • coordinate with QA re: talos suite that will run the jetpack-sdk with tip build.

Done:

  • mozilla-1.9.3 was put into production (then backed out)
  • twig repos are live
  • planning jetpack-sdk branch/test suite

Next:

  • tryserver unittests over to talos-r3 masters
  • turn on Jaegermonkey in production
  • re-enable mozilla-1.9.3 as mozilla-2.0
  • send try tests to talos-r3 masters
  • start staging private repo and jetpack repo -- look into special steps that Warner has going on
  • add more slaves to talos-r3 pool

Done:

  • minis added to try builder pool
  • testing mozilla-1.9.3 in staging
  • various reviews and putting out of small fires for try

Next:

  • put into production mozilla-1.9.3
  • put into production twigs
  • get private repo in staging
  • tryserver unittests sent over to talos-r3

Coordination:

  • coordinate with catlee's rollout of scheduler db and a new talos-master to handle load from try sending unittests to talos

Done:

  • repos created for 1.9.3, twigs, and jaegermonkey - staging env set up in schedulerdb-land
  • added more mac slaves to try pool (10)
  • removed try-staging and cleaned up staging of try related files

Next:

  • mozilla-1.9.3 branch mozconfigs, talos configs, release configs, mobile configs ready
  • twigs - sign up & docs ready, mozconfigs, talos set up
  • jaegermonkey mozconfigs, talos set up & moved to production
  • add 10 more minis to the try builder pool

Done:

  • new linux try slaves up
  • matched unittest_suites for try to m-c's set
  • added try masters to test-masters.sh

Next:

  • 1.9.3 branch
  • wood branches
  • remove try-staging and clean up staging of all try related stuff

Done:

  • fixed try email output & who the emails were sent to
  • more blogging and information sharing about new try
  • negotiating getting more slaves on try and being able to send try unittests to talos (when the load can be handled)
  • buildduty

Next:

  • work on wood branches
  • 1.9.3 branch
  • attach new slaves to try as they are created
  • push to try being able to select specific builders

Done:

  • try-as-branch went live
  • talos-r3 for try-as-branch
  • new slaves (all but mac) re-imaged and attached to try-master
  • blogged and finished wiki instructions
  • fixed merging packagedUnittest builds
  • fixed email output for test builds (mochitest chunks)

Next:

  • get the try-mac slaves online
  • possible try downtime to reset the master due to backed up try builds
  • fix the email output for tests other than mochitest
  • fix the email of try notifications to the pusher, not the changeset author
  • start planning wood branches
  • buildduty

Done:

  • ftp account for trybld is up and working
  • approx. half of try slaves are being re-imaged to go into the new try pool

Next:

  • fix symbol uploads for win32
  • xpcshell tests on linux are failing
  • talos for try-as-branch
  • get new slaves attached to pm02 try-trunk-master
  • continue documenting and finalize instructional docs & blog post

Done:

  • talked at dev meeting about tryserver rollout
  • pulled 1 slave of each platform from current-try & filed bug to re-image
  • created try-trunk-master on pm02 (port 9011) and it's ready for slaves
  • buildbotcustom patches are checked in
  • production config patches ready (waiting to be tested)

Next:

  • write blog posts for how to use new try master and what to expect (custom mozconfigs)
  • work on separating out the platform/unittest requests from hg comments
  • still waiting to test production configs (blocked on trybld acct on ftp.m.o)
  • once ftp account is ready, test production configs - iron out any network/firewall kinks

Done:

  • lightning talk about upcoming try rollout
  • custom mozconfig patches tested and checked in
  • [tested] fix for setting of revision when long hash is returned for linux/mac
  • [tested] fix for sendchanges to add testsUrl
  • upload paths working
  • graphserver updated for upcoming try rollout

Next:

  • finalize patches after fixing revision setting on win32, and also setting 'who' for forced builds from waterfall
  • create new try-master (on pm02?)
  • double-check graphserver entries for 10.6 (it's currently 10.6.2) and make sure it doesn't need renaming
  • check-in patches for buildbotcustom, tagging the current version old-try is using
  • talk at developer meeting about upcoming try rollout
  • blog about upcoming try rollout
  • pull and re-assign try slaves to new try master
  • Do the try rollout.

Done:

  • turned off unittests on production master for m-c macosx
  • tryserver custom mozconfig works via push-to-try
  • releng moto

Next:

  • testing on try-staging still * added logic to try build factory the second testsUrl file in the sendchange * test mozconfig failure ** force build from buildbot
  • prepare for tryserver-as-branch rollout

Done:

  • buildduty
  • do-over of 3.0.19 sums and pgp sigs
  • 3.7a4 release
  • fixed uploading codesighs.log for tryserver

Next:

  • attempt 3 at turning off the m-c macosx unittests on production-master
  • tryserver custom mozconfig
  • need to fix the pushlog for try-staging

Coordination:

  • getting the old staging-try slaves to be just like moz pool slaves so they can rejoin the pool (waiting on IT)

Done:

  • packaged unittests on talos for m-c macosx is in production
  • 3.0.19 release
  • 3.0.19 -> 3.6.3 MU snippets
  • try-staging is not doing per-change build anymore tipsOnly ftw
  • disabled tjss

Next:

  • testing custom mozconfig in try-staging
  • continuing to work on getting more platforms added to talos-unittest
  • turning off talos-staging-master/talos-master02
  • buildduty
  • turn off unittest-on-builders for mac m-c

Done:

  • ran unittests manually on OS X
  • tested try builds, got noMerge working
  • mailNotifier for Try builds can handle %(got_revision)s in extraHeaders if it's not set yet when build fails
  • addonsmgr branch is live

Next:

  • get linux & mac packaged unittests running in talos-staging-master
  • 3.0.19 release
  • try-staging is doing per-change builds
  • try-staging needs to handle custom mozconfigs

Done:

  • Addonsmgr tested in staging
  • Try-as-branch non-affecting code checked in

Next:

  • Cleaning up production patches for Addonsmgr
  • Downtime on Thursday to turn it on
  • Fix MailNotifier to handle extra headers in Try emails
  • Testing to make sure Try builds are non-merging
  • Run unittests manually on 10.5/10.6 boxes

Next:

  • Nanojit/Addonsmgr branches up in staging
  • Try-as-branch unittest and emails working, clean up patches, get in production by week's end
  • Unittests running manually on OSX 10.5/10.6 minis

Done:

Try uploads working (post_upload.py) Self/Peer review

Next:

Confirm the install instructions for 3.6 CD and send copy to producer Try emails need to use ftp url not staging-stage Make sure packaged unittests are triggered by try builds (last linux build didn't trigger reg. pkg tests, just opt-debug) Push to try from web interface Nanojit-central branch

Done:

Lorentz branch - bug 536188

Next:

Try uploads Firefox 3.6 CD Self/Peer review Nanojit-central branch/JagerMonkey branch Push to try from web interface (sendchange.cgi)

Done:

Next:

Done:

  • misc.py now handles turning nightly/l10n nightlies on and off through config.py flag
  • registered for FOSDEM & PyCon
  • Next:

  • Still tweaking turning off nightly builders through config.py
  • Land bug 520903 and bug 535896 so that the path to 520227 is less cumbersome
  • Work out the emails from new tryserver-as-branch
  • Create list of bugs that could be good sprint material for PyCon