Buildbot/Talos/Misc: Difference between revisions

Line 5: Line 5:


== Steps to add a test ==
== Steps to add a test ==
* file a bug to add appropriate rows to [http://hg.mozilla.org/graphs/file/tip/sql/data.sql graphserver].
* File a bug to add appropriate rows to [http://hg.mozilla.org/graphs/file/tip/sql/data.sql graphserver] [[example]].
** file an additional IT bug to deploy the sql changes on the production and staging graph servers
** File an additional IT bug to deploy the sql changes on the production and staging graph servers [[example]].
** if this is adding new pages, ensure these sql changes include [http://hg.mozilla.org/graphs/file/5dd6f4fb9c27/sql/pages_table.sql page definitions]. NOTE: this one detail is usually forgotten since it is so rare
** If this is adding new pages, ensure these sql changes include [http://hg.mozilla.org/graphs/file/5dd6f4fb9c27/sql/pages_table.sql page definitions]. NOTE: this one detail is usually forgotten since it is so rare
** MOBILE ONLY: if we are changing/adding pages which mobile tests use or need, you need to update bm-remote [[https://bugzilla.mozilla.org/show_bug.cgi?id=883896 example]]
* file a bug to add tests to [http://hg.mozilla.org/build/talos/file/tip/talos/test.py talos].
* file a bug to add tests to [http://hg.mozilla.org/build/talos/file/tip/talos/test.py talos].
* create a talos.zip file and file a releng bug to upload it to the build network
* create a talos.zip file and file a releng bug [[https://bugzilla.mozilla.org/show_bug.cgi?id=873180 example]] to upload it to the build network
** NOTE: for aurora/central on desktop only - we update testing/talos/talos.json with a revision to the talos tree [[example]]
** NOTE: for other branches or mobile - we still need an updated talos.zip, many times we need to update both [[example]]
* create a patch for buildbot to add a definition of this new test and turn it on for the current branch
* create a patch for buildbot to add a definition of this new test and turn it on for the current branch
* create a m-c (not inbound) patch to modify testing/talos/talos.json, get it reviewed and landed
** NOTE: for aurora/central on desktop only - we update testing/talos/talos.json with a revision to the talos tree [[example]]
** NOTE: one exception is adding an entirely new suite- this requires a buildbot patch to add the new scheduled job [[example]]
** NOTE: for other branches or mobile - we still need a buildbot patch, many times we need to update both
* create a mozilla-inbound patch to modify testing/talos/talos.json, get it reviewed and landed
* create bugs for each time we uplift from mozilla-central->aurora->beta->release->esr to turn on your test
* create bugs for each time we uplift from mozilla-central->aurora->beta->release->esr to turn on your test
* if this is an update to an existing test that could change the numbers, this needs to be treated as a new test and run side by side for a week to get a new baseline for the numbers.
* if this is an update to an existing test that could change the numbers, this needs to be treated as a new test and run side by side for a week to get a new baseline for the numbers.
Confirmed users
3,376

edits