All articles tagged as:

selfserve-agent

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: If no new try job to mess with, then submit one, see ReleaseEngineering/TryServer   hg clone http://hg.mozilla.org/mozilla-central 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://hg.mozilla.org/try/ In my case you can see the try job running here:https://tbpl.mozilla.org/?tree=Try&rev=3a5e6ca198d8   If the push is successful it'll give you you…

Read more »

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 stan…

Read more »