75
edits
New test environments: Difference between revisions
add preparation work
(→Task Overview: bring title in line with header title) |
(add preparation work) |
||
| Line 39: | Line 39: | ||
** responsibility: CI-A | ** responsibility: CI-A | ||
** task checklist: [[New_test_environments#Checklist_6|patch checklist]] | ** task checklist: [[New_test_environments#Checklist_6|patch checklist]] | ||
= Preparation work = | |||
The underlying test environment must first be set up. | |||
At Mozilla there are two different machine types, both self-explalanatory: | |||
* virtual | |||
* hardware | |||
Both require different approaches. | |||
== Hardware == | |||
The availability of test hardware is outside of CI-A (and therefore your) control. With some exceptions, Mozilla's server farms are managed by the Release Engineering team. They work in concert with CI-A to develop a plan to upgrade and maintain test hardware. | |||
For instance, the OS upgrade from macosx1010 to macosx1014 was handled by :dividehex. See [https://bugzilla.mozilla.org/show_bug.cgi?id=1530474 Bug 1530474]. | |||
With some exceptions, CI-A is not particularly involved in this process. | |||
== Virutal == | |||
For virtual test environment, it is within the scope of CI-A work. | |||
Examples: | |||
* [https://phabricator.services.mozilla.com/D41638|debian10-iris] | |||
* [https://phabricator.services.mozilla.com/D42597|debian10] | |||
Both examples involve the creation of new docker images that run on AWS instances. | |||
= Enable platform on taskgraph = | = Enable platform on taskgraph = | ||
The first step of any new test environment is to enable the test platform on Tryserver. | The first real step of any new test environment is to enable the test platform on Tryserver. | ||
At the bare minimum, ensure the taskgraph is sound with each step. This can be verified using <code>./mach taskgraph full -v</code> | At the bare minimum, ensure the taskgraph is sound with each step. This can be verified using <code>./mach taskgraph full -v</code> | ||