Wikimedia Release Engineering Team/Checkin archive/20130924

Previous: https://www.mediawiki.org/wiki/Wikimedia_Release_%26_QA_Team/Checkin-20130917

Agenda

Improve our deployment process

• git-deploy
  • git-deploy with rsync: https://bugzilla.wikimedia.org/show_bug.cgi?id=54185
  • corrupted objects: https://bugzilla.wikimedia.org/show_bug.cgi?id=51142
• automation
  • List of items/roadmap to get Selenium tests triggered from Gerrit. https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests
  • we have first passing tests at https://integration.wikimedia.org/ci/job/qa-browsertests-run/ (thanks to Antoine)
    • Still need some tuning thoug =)
  • For now, runs on every commit sent to qa/browsertests.git. Can be retriggered manually.
• monitoring
  • nothing specific this week

Take the Beta Cluster to the next level

• monitoring of fatals, errors, performance
  • https://bugzilla.wikimedia.org/show_bug.cgi?id=52357 "Set up graphite monitoring for the beta cluster"
    • more on Ariel's lap
    • Ops migrating graphite/statsd in production. Might want to poke them to install one in labs as well.
• add more automated tests for eg the API
  • Article syncing https://bugzilla.wikimedia.org/show_bug.cgi?id=49779
• feed experiences/gained knowledge of Beta Cluster automation up to production automation

Better align QA effort with high profile features

• Apply model of Language/Mobile embedded QA to a new feature team (specifically VisualEditor)

Chris has been screening candidates for this position daily since last week.

• Include more user contributed code testing (eg: Gadgets)

http://lists.wikimedia.org/pipermail/qa/2013-September/000449.html (no response so far)

• Increase capacity through community training for browser tests

had a nice turnout for this: http://www.meetup.com/wikimedia-tech/events/137381022/ Note: Erik and Arthur have proposed a tactical/communications meeting among at least some of the feature teams and the non-specific teams (ops, analytics, Language) possibly to be called a "Scrum of scrums". I think it would be valuable to have a RelEng/QA presence there in the service of "high profile features".

Misc

• FYI: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_now_opt-in_only_for_all_users_on_English_Wikipedia
  • Andre offered a summary. Similar issues between VisualEditor and ULS.
  • Antoine: that is mostly "internal" drama. Think about the half billion readers \O/
• Mobile on Train?

- RT ticket in for getting MobileFrontend configured on Test2
- After this is set up I need to setup a new jenkins job that runs against Test 2 
- Will work with Greg to find out when code changes go out so that I can make sure to do a few extra passes at testing after the first few releases

• Flow i18n messages are missing on beta
  • The extension is not registered in the extension-list and its messages are ignored by the cache builder. Sam has send a few patches:
  • https://gerrit.wikimedia.org/r/#/c/84900/
  • https://gerrit.wikimedia.org/r/#/c/84897/
  • https://gerrit.wikimedia.org/r/#/c/84898/