ReferencePlatforms/How To/Setup a New Reference Platform: Difference between revisions

ReferencePlatforms/How To/Setup a New Reference Platform (view source)

249 bytes added , 27 February 2013

Confirmed users

3,990

edits

@@ Line 43: / Line 43: @@
 * testing machines and each type of build need graph server changes
-** graph server work needs to be run on staging and production graph server
+** You can insert graph changes by logging to slavealloc
-** need to land changes to 'sql/data.sql' on the default branch of http://hg.mozilla.org/graphs.  Example {{bug|783660 }}  This bug should be approved opened in the Server Operations: Database bucket but the patch should be approved by a releng person.
+** graph server work needs to be run on staging (graphs_mozilla_org_new) and production (graphs_stage2_prod) graph server
+** need to land changes to 'sql/data.sql' on the default branch of http://hg.mozilla.org/graphs (to match your inserts).
 ** If this is a new build platform, make sure that graph server knows about the build platform
-** Also, you'll need to open a bug with Server Operations: Database to add the new machines to the graphs.mozilla.org and graphs.allizom.org.  Example {{ bug|784330 }}
+*** insert a machine name like %OS%_%branch% (e.g. "WINNT_5.2_mozilla-central" and "WINNT_5.2_mozilla-central_leak_test")
+For example:
+<pre>
+tart transaction;
+insert into os_list values (null, "WINNT 6.2 x64");
+SET @lastid = LAST_INSERT_ID();
+insert into machines values (null, @lastid, 0, "2.67", "t-w864-ix-001", 1, unix_timestamp());
+insert into machines values (null, @lastid, 0, "2.67", "t-w864-ix-002", 1, unix_timestamp());
+commit;
+</pre>
 == Open a bug for tbpl changes ==