Manual Testing of Arbitrary Builds

When a new selfserve-agent change is pushed to production, it's necessary to verify functionality with some maual testing. Here are some steps to basic testing:

  1. If no new try job to mess with, then submit one, see ReleaseEngineering/TryServer


    • hg clone
    • cd mozilla-central
    • echo "THING" >> README.txt
    • hg qnew test-patch
    • hg qref –message "try: -b o -p linux64 -u none -t none"
    • hg push -f ssh://
  2. In my case you can see the try job running here:


    • If the push is successful it'll give you your own link
  3. Submit a blank arbitrary job request to x86-64 try build/3a5e6ca198d8 using
  4. python –buildername "Linux x86-64 try build" –branch try –rev 3a5e6ca198d8


    • Leaving –file out so that files = []
  5. See running job here
  6. Check for pending job at
  7. Also check
  8. Check buildbot status can be found by finding the appropriate master on the buildapi page

Vagrant can now run BuildAPI and RabbitMQ apps

Continuing on from my previous post, I verified that buildapi and selfserve-agent are truly connected and able to exchange over the amqp, and that the entire buildapi application is running well by running similar procedures that work in my local setup.

Once I did that I updated the Vagrantfile to forward the vagrant port 8888 to the host port 8888, and to build and start the rabbitmq-app and buildapi-app. In the wild, the Vagrantfile will not be having docker build the docker images, but rather it will pull them from Mozilla's docker repository, which will be a much faster process. As it stands, running vagrant up from scratch the first time will take about 10-15 minutes to launch.

Here's how you can NOW run a fully functional BuildAPI app locally with a single command :)

  1. hg clone
  2. cd vagrant-docker-setup
  3. vagrant up