User:NThomas:OnceAgain

From MozillaWiki
Jump to: navigation, search

<blink> This page is a work in progress. Some of the changes were moved over 24 May 2015. </blink>

Name: Release Engineering (#)
Description: Continuous automation of compilation and testing for desktop and Android applications, where not covered by a submodule
Owner: Nick Thomas
Peer(s): Ben Hearsum, Chris Cooper, SOME NEW PEERS
Source Dir(s): browser/config/mozconfigs/, mobile/android/config/mozconfigs/, xulrunner/config/mozconfigs/, b2g/config/, tools/update-packaging/, build/tools, build/buildbotcustom, build/buildbot-configs
Bugzilla Component(s): Release Engineering::Buildduty, Release Engineering::General Automation, Release Engineering::Load Requests, Release Engineering::Other, Release Engineering::Platform Support, Release Engineering::Tools
URL(s): https://wiki.mozilla.org/ReleaseEngineering
Discussion Group: release-engineering

Submodules

Name: Release Engineering: Mozharness (#)
Description: A configuration-driven script harness for running mozilla builds and tests
Owner: TBD
Peer(s): TBD
Source Dir(s): build/mozharness
Bugzilla Component(s): Release Engineering::Mozharness
URL(s): https://wiki.mozilla.org/ReleaseEngineering/Mozharness
Discussion Group: release-engineering
Name: Release Engineering: Release Automation (#)
Description: Automation to create desktop & Android release/beta/ESR bits
Owner: TBD
Peer(s): TBD
Source Dir(s): ship-it, releaserunner, parts of buildbotcustom and buidlbot-configs
Bugzilla Component(s): Release Engineering::Release Automation, Release Engineering::Releases, Release Engineering::Releases: Custom Builds
URL(s): https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain
Discussion Group: release-engineering
Name: Release Engineering: Puppet (#)
Description: Configuration management for servers and CI workers
Owner: Dustin Mitchell
Peer(s): TBD
Source Dir(s): build/puppet
Bugzilla Component(s): Infrastructure & Operations:: RelOps: Puppet
URL(s): https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain
Discussion Group: release-engineering
Name: Release Engineering: Balrog (#)
Description: A database-backed update server to replace AUS2
Owner: TBD
Peer(s): TBD
Source Dir(s): balrog, balrog-ui
Bugzilla Component(s): Release Engineering::Balrog: Backend, Release Engineering::Balrog: Frontend
URL(s): https://wiki.mozilla.org/Balrog
Discussion Group: release-engineering

Notes

  • other repositories which are too small to warrant a separate module at this point: buildapi, cloud-tools, funsize/funsizer, fwunit, mozpool, relengapi, cleanslate+runner, slave_health, slaveapi, treestatus
  • talos could go to a-team instead of sharing, based on recent commits