Confirmed users
9,511
edits
New test environments: Difference between revisions
→Overview
(→Green up tests: expand section) |
|||
| Line 3: | Line 3: | ||
From time to time, there rises a need to upgrade the underlying operating system of a platform. This need arises in sync with new major releases of various operating systems that form part of the CI infrastructure. | From time to time, there rises a need to upgrade the underlying operating system of a platform. This need arises in sync with new major releases of various operating systems that form part of the CI infrastructure. | ||
For instance, as of 2019-08-07, all Firefox builds for Linux | For instance, as of 2019-08-07, all Firefox builds for Linux are executed on Ubuntu 16.04.5 docker containers. In other words, the version of Linux distribution used for testing is at least 2 major releases behind the likely dominant version on the market, which is Ubuntu 18.04. | ||
Upgrade of the underlying operating system version has been, in the past, considered a large undertaking often taking upwards of 6 months. This causes a chicken-and-egg problem where regular upgrades do not occur due to the perceived amount of work, which in turn | Upgrade of the underlying operating system version has been, in the past, considered a large undertaking often taking upwards of 6 months. This causes a chicken-and-egg problem where regular upgrades do not occur due to the perceived amount of work, which in turn causes the amount of issues to multiply once the upgrade is finally tackled. | ||
The aim of this document, and process is to establish a standardized process | The aim of this document, and process is to establish a standardized process which can be used by anyone in Mozilla engineering to perform operating-system upgrades. | ||
= Task Overview = | = Task Overview = | ||