ReleaseEngineering:Contribute

Welcome!

As a contributor to our team you will be part of assisting a globally distributed team of Release Engineers responsible for all software source code, automated test infrastructure, and build and deployment processes for Mozilla’s extensive Build Infrastructure of roughly 1,250 machines (Linux32/64, Mac ppc/32/64, Windows32/64, Maemo and Android). You’ll help us write code in Python to develop and maintain application tools that build, deploy, automate and streamline code management for desktop, and mobile, Firefox. We have far too many users to efficiently build and test our products by hand; automation of current and future release processes is a key.

We need YOUR help

So many projects aimed at improving our infrastructure, so short on time and resources. We have over 600 bugs as of this writing that currently are unassigned while we work on what's most urgent to the Mozilla mission. Many of those bugs are ones that require access to some firewalled network machines but we also have projects that can be worked on out in the open that would greatly improve the lives of developers who are trying to get features and fixes out to our product users fast & reliably.

Projects

Try Server

• Current contributors:
• Check the list of open bugs on enhancing our current Try system. See if there's a bug that interests you. Many of these are smallish bugs that would enable you to learn how to set up a local buildbot instance for testing and then provide usable patches to our custom buildbot code.
  • Instructions on how to set up a local testing evironment (which only work if you are a MoCo RelEng employee)
• We use a trychooser to do syntax parsing and that module would even better as a pip package so it can be installed and imported into multiple tools. We're currently re-implementing this code several times across our code base.

Autoland

• Current contributors: Marc Jessome
• Bug fixing, preparing for beta-test live on bugzilla. Currently only being run in a staging environment.
• Code is on github
• Project Description and tracking bug 657828

Setup a personal development environment

Because the instructions for setting up a master assume you have root on a machine inside the build network, your first step is to become a MoCo RelEng employee.

You'll want to clone our buildbot-configs (default branch) from here: http://hg.mozilla.org/build/buildbot-configs/

hg clone http://hg.mozilla.org/build/buildbot-configs

Then follow the instructions here How To Setup a Personal Development Master to get set up with a buildbot master.

You can also create a local instance of a build slave for testing your work, you'll need to install buildbot-slave in your virtualenv

pip install buildbot-slave

Then create an instance of a buildslave and configure it to connect to the master. You'll want it to match the slave names we use in our configs (test or builder)

Come find us in irc.mozilla.org channel: #build with your questions, we want you to be able to successfully work on code and submit useful patches so don't be afraid to ask about whatever is blocking you.

Get in touch

If you're interested in helping out with some RelEng bugs please get in touch with Lukas Blakk (lsblakk) or Armen Zambrano (armenzg) either through email or IRC (irc.mozilla.org, join #build)