« Back to home

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  

  2. hg clone http://hg.mozilla.org/mozilla-central

  3. cd mozilla-central
  4. echo "THING" >> README.txt
  5. hg qnew test-patch
  6. hg qref –message "try: -b o -p linux64 -u none -t none"
  7. hg push -f ssh://hg.mozilla.org/try/
  8. In my case you can see the try job running here:https://tbpl.mozilla.org/?tree=Try&rev=3a5e6ca198d8  

  9. If the push is successful it'll give you your own link

  10. Submit a blank arbitrary job request to https://secure.pub.build.mozilla.org/buildapi/self-serve/try/builders/Linux x86-64 try build/3a5e6ca198d8 using triggerarbitraryjob.py
  11. python triggerarbitraryjob.py –buildername "Linux x86-64 try build" –branch try –rev 3a5e6ca198d8  

  12. Leaving –file out so that files = []

  13. See running job here https://secure.pub.build.mozilla.org/buildapi/revision/try/3a5e6ca198d8
  14. Check for pending job at https://secure.pub.build.mozilla.org/buildapi/self-serve/try/rev/3a5e6ca198d8
  15. Also check https://tbpl.mozilla.org/?tree=Try&rev=3a5e6ca198d8
  16. Check buildbot status can be found by finding the appropriate master on the buildapi page https://secure.pub.build.mozilla.org/buildapi/revision/try/3a5e6ca198d8