Zephyr and FreeRTOS jobs do not require 16GB of RAM to build and
constitute the bulk of our CI (by number) quota usage. By moving them to
smaller instances, with 4GB of RAM, we can use the remaining quota
better.

On the infrastructure side we now have a new auto-scaling pool, with
s3.large.2 instances. Those join the existing s3.xlarge.4 (formerly
known as "heavy") and s3.large.8 (formerly known as "light").

The .workspace job uses the s2.large.8 by default, making a safe (but
expensive) default. Specific jobs deviate as follows:

 - zephyr and freertos jobs use s3.large.2
 - two blueprint jobs with more recipes use s3.xlarge.4

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This was missed as CI was not operational during the big move.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Most things are moved unchanged. The relatively few changes are to the
documentation, as the split between the meta-ohos and manifest is gone,
as well as to the actual CI definitions for the workspace directory,
since the sources/ sub-directory is gone, and there was some
backwards-compatibility code that no longer makes sense to maintain.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

The .ostc-ci directory becomes .oniro-ci

The various CI variables names are now all uniformly named CI_ONIRO_.
Some specific variables were further trimmed to avoid using "CI" twice.

Remaining uses of OSTC and OHOS are for URLs, container images and
branch names.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

* All project name replaced with tag
* definitions.rst reference added
* Closes: OSTC/OHOS/docs#77

Signed-off-by: Gururaj Shetty <gururaj.shetty@huawei.com>

Andrei Gherzan authored 3 years ago and Stefan Schmidt committed 3 years ago

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Nagesh Shamnur <nagesh.shamnur@huawei.com>

The OS will start to depend on a specific partition table and having to
maintain multiple qemu setups might not prove useful. Also, we have
encountered issues trying to boot wic images (disk images as opposed to
root filesystems) with qemu ARM machines.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Raspberry Pi 4 was added a while ago but is not a part of CI.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Currently machines and flavours are defined in the meta-ohos repository
but their CI pipelines are defined in the manifest repository. Move the
definitions of the various build jobs here to be included from the
manifest repository internally.

This way the public interface is unchanged but patches such as the
recent Raspberry Pi 4 support can enable a new MACHINE configuration and
a new CI job all in one go, to the extent that in-progress CI will pick
it up.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/44


Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>