ReleaseEngineering/Tupperware: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 59: Line 59:
ex. Buildbot is not visible at http://127.0.0.1:8000/
ex. Buildbot is not visible at http://127.0.0.1:8000/
* If the others are up and Buildbot is not, then run "vagrant ssh", then "docker restart buildbot"
* If the others are up and Buildbot is not, then run "vagrant ssh", then "docker restart buildbot"
== Error: machine is in the 'poweroff' ==
When running "vagrant up", I am getting a error which states, "The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again."
There are a few possibilities:
* OS X Mavericks may be causing problems with the 64-bit vagrant boxes (https://github.com/mitchellh/vagrant/issues/2157)
** could be a missing kernel driver, there is a hidden virtualbox GUI window that will give more information on errors
* Make sure you are running
** Vagrant 1.6.3+
** VirtualBox 4.3.6+
* Switching to a 32-bit vagrant box seems to be a temporary fix

Revision as of 18:08, 23 June 2014

Overview

                           _._                                                  
                      _.-``__ -._                                             
                 _.-``.-```  ```-. -._           
             .-`` .-``            ``._  -._                                   
            (    '                    `,      `.     
            |`-._ `-._               _.'  _.--'     
             `-._`-._ `-._       _.-' _.-'_.         
              |  `-._`-._ `-._.-'_.-'_.-'  ,                                    
               \     `-._`-.__.-'_.-'     /                                   
                `-.      `-.__.-'      .-'                                     
                   ``-.            .-                                 
                       ``-.    .-            
                           ``
 _______                                                 
|__   __|                                                
   | |_   _ _ __  _ __   ___ _ ____      ____ _ _ __ ___ 
   | | | | | '_ \| '_ \ / _ \ '__\ \ /\ / / _` | '__/ _ \
   | | |_| | |_) | |_) |  __/ |   \ V  V / (_| | | |  __/
   |_|\__,_| .__/| .__/ \___|_|    \_/\_/ \__,_|_|  \___|
           | |   | |                                     
           |_|   |_|                                              

Mozilla apps in Docker. Portable, Reusable, and Containerized.

Great for keeping an unpolluted development environment, testing patches and enabling new contributors to join the effort by lowering the barriers to entry (being one of the biggest deterrents to potential new contributors).

Vagrant is used as a quick and easy way to provision the docker apps and make the setup truly plug n' play. The current setup only has a single Vagrantfile which launches BuildAPI and BuildBot, with their dependency apps RabbitMQ and MySQL.

Project Requirements

There is only a single project dependency that you have to worry about

Currently Included Apps

Currently Tupperware is used for only Release Engineering apps, but that is not meant as a preclusion to avoid other apps, so by all means add some!

Currently included Mozilla apps:

Dependency apps currently included:

Getting Started

How to run:

  • Install Vagrant 1.6.3
  • hg clone https://hg.mozilla.org/build/tupperware/ && cd tupperware && vagrant up
    • (takes >10 minutes the first time)

Where to see apps:

Troubleshooting Tips

App not visible?

ex. Buildbot is not visible at http://127.0.0.1:8000/

  • If the others are up and Buildbot is not, then run "vagrant ssh", then "docker restart buildbot"

Error: machine is in the 'poweroff'

When running "vagrant up", I am getting a error which states, "The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again."

There are a few possibilities:

  • OS X Mavericks may be causing problems with the 64-bit vagrant boxes (https://github.com/mitchellh/vagrant/issues/2157)
    • could be a missing kernel driver, there is a hidden virtualbox GUI window that will give more information on errors
  • Make sure you are running
    • Vagrant 1.6.3+
    • VirtualBox 4.3.6+
  • Switching to a 32-bit vagrant box seems to be a temporary fix