ReleaseEngineering

About Us

We ship Firefox to the world!

Release Engineering does this by:

• Developing world-class, scalable, open, secure, and maintainable infrastructure for application builds and tests, on a diverse set of desktop and mobile platforms

• Building fast and reliable pipelines to transform source code into shipped products

Contacting Release Engineering

Our team is located on 3 continents and in 4 time zones. This allows us to provide better service, especially if you contact us using one of the following methods:

• To request a new service, please file a bug
• To ask a general question, ping in #releng on IRC, or email release@m.c
• To request status on an existing request, set the "needinfo" flag in the bug.

Our team works normal business hours for our respective time zones. If you need to escalate an issue that is both urgent and important, use the following methods:

1. Use #releng in IRC or email release@m.c, starting your message with 'URGENT:'. If no response in 15 minutes, then
2. Be sure the bug severity is set to "blocker"
3. Call one or more of the following people (nagios page preferred if you have access):
   • Chris AtLee Eastern Time

If you get voice mail, please leave your callback number.

Contributing

If you are interested in getting involved with Release Engineering, please see our contributing page! We'd love to hear from you.

Team

Mozilla's Release Engineering:

• twitter: @MozRelEng
• blogs: Planet Release Engineering
• calendar: Google Calendar
• mailing list: release-engineering@lists.mozilla.org

Name	Profile	Twitter	Blog
Ben Hearsum	bhearsum	@bhearsum	Ben's blog
Justin Wood	Callek		"Callek's Blog"
Chris AtLee	catlee	@chrisatlee	chris' random ramblings: programming, photography, media, and anything else that strikes my fancy
Jordan Lund	jlund
Kim Moir	kmoir	@kmoir	Releng of the Nerds
Michael Shal	mshal		Mike Shal's blog
Nick Thomas	nthomas	@nthomasftang	F'tang F'tang Release wrangling at the bottom of the world
Rail Aliiev	rail	@railaliiev	Rail's blog
Aki Sasaki	aki	@escapewindow	escapewindow
Mihai Tabara	mtabara	@mihaitabara
Rok Garbas		@garbas	Rok's blog
Johan Lorenzo	jlorenzo		Johan's blog
Simon Fraser	sfraser

Interns

• Interns

Documentation

• How Tos - a collection of instructions for specific tasks
• Releng Docs for overviews, details, and background.
• Development Best Practices - read this when you're starting something new
• Wiki Guidelines - how to wiki garden for fun and profit
• Applications - Various applications and services that RelEng provides
  • Deployment - How we deploy our tools, and how do we update them.
• Overview Architecture Diagram - an architecture diagram that gives a high level overview of systems involved in producing releases of Mozilla's software

• Buildbot Migration - What builds are produced where? Buildbot, TaskCluster, or other?

Buildbot

• Master
  • Master Naming
  • Master Setup
  • Upgrading Buildbot
  • Preproduction
  • Masters (authentication required)
  • Queue directories
• Slave
  • Buildslave Versions
  • Buildslave Startup Process
  • Slave naming
• Development
  • Virtualenv - How to set up and use python virtual environments
  • Methods for testing your changes
  • Buildbot Best Practices
  • Landing Buildbot Master Changes
• References
  • Buildbot Database Schemas

Taskcluster

• • Taskcluster docs
  • Taskcluster tools
  • Verification steps for a new taskcluster platform

Releases

• Release Checklist and Build Notes
• Releng Post Mortem Meetings
• What is releaseduty?
• Release Promotion
• Update Generation
  • Patcher tags for release updates

Platform Support

• Reference Platforms
• Slave Allocator
• Official Platform Support Checklist

Configuration Management

• PuppetAgain

Buildduty

• Check Buildduty manifesto
• Check Buildduty actionable
• How To: So you're on buildduty...
• Managing Buildbot with Fabric
• Treeherder wiki page
• Clobbering the Tree
• Bug Triage
• RelEng+IT shared downtime
• Project Branch Planning: how to request a new project branch
  • Disposable Project Branch Bookings
• Build and Test Log Error/Warning Reference: Debugging red and orange in results

Tryserver

• Tryserver As Branch
• TryServer
• TryChooser

Testing

• Graph Server Notes
• Intermittent Errors
• Requesting A Slave
• Testing a new Signing Server

Bugzilla

• Flags
• Whiteboard
• Triage

VCS Sync

• HowTo
• History

Subpages

• ReleaseEngineering/Breakout Sessions
• ReleaseEngineering/Blackbox Sessions
• ReleaseEngineering/Presentations
• ReleaseEngineering/Obsolete Pages
• Special:PrefixIndex/ReleaseEngineering/ - all subpages of ReleaseEngineering in the wiki
• ReleaseEngineering/NoReboots
• day 1 checklist
• day -1 checklist