ReleaseEngineering/How To/Trigger Talos Jobs: Difference between revisions

ReleaseEngineering/How To/Trigger Talos Jobs (view source)

920 bytes added , 18 August 2011

no edit summary

Confirmed users

1,377

edits

@@ Line 15: / Line 15: @@
 * copy that sendchange command and run it on any master's command line
 * rinse/repeat
+=Triggering addition Talos/Test runs for a try build=
+* When someone pings you in #build with their try run dir name (format: $email-$changeset eg: lsblakk@mozilla.org-4asf23fsd251d):
+*Either:
+**ssh into production-master{01,02,03}
+**OR run from your machine tools/buildfarm/maintenance/try_sendchange.py
+***on the production-masters, there is a ~/try_sendchange.sh wrapper script which uses argparse in /tools/buildbot-0.8.0/bin/python
+Then run:
+ # Add a -n to get a --dry-run or --help for more info.
+ # get all talos runs available (based on ftp dir for that build, so you can't do it before the builds are there)
+ ./try_sendchange.sh $email-changeset -t all
+ # OR to do custom set of talos suites
+ ./try_sendchange.sh $email-$changeset -t scroll,svg,nochrome
+ # NOTICE no spaces between comma-separated suite names!
+*It will spew back to you all the sendchanges it does (or will do if you are in dry-run mode).