Project 'eclipse/oniro-core/meta-openharmony' was moved 
to 'eclipse/oniro-oh/meta-openharmony'. Therefore updating
links and references accordingly.

Signed-off-by: Francesco Pham <francesco.pham@huawei.com>

This is needed in order to enable creation of tap devices, which we want to
use for running ACTS against QEMU machine.

Signed-off-by: Esben Haabendal <esben@geanix.com>

With this change, we will be able to schedule lightweight and heavy jobs on
different runners, thus speeding builds by providing more runners for
lightweight jobs, while controlling cpu resources for each job so that each job
get a fair share.

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

This is breaking builds, and fetching from main npm repository is working
fine...

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

While we still need to use an external Docker registry, we don't have
to hardcode it, and we don't need to push to external git repository
to update it.  By manually setting CI_REGISTRY, CI_REGISTRY_USER,
CI_REGISTRY_PASSWORD and CI_REGISTRY_IMAGE variables, we can build and
push from gitlab.eclipse.org pipeline.

And with this change, anybody forking meta-openharmony will be able to
use the Docker registry included with their GitLab instance if they
want to.

The downside is that forks on gitlab.eclipse.org needs to setup
CI_REGISTRY_IMAGE variable to get working CI.

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

We will be using flex-native and bison-native recipes instead from now on.

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

Although not covered by the official OpenHarmony documentation, the ruby
interpreter and cpio tool is used during build.

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

Fetch OpenHarmony OS codebase release tarballs and test
oniro-openharmony-toolchain and oniro-openharmony-bundle against these.

In order to save CI resources, only MR pipelines run these new jobs
automatically.  For normal branch pipelines, the job are set to manual, so
developer can choose to run them as needed.

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

We will be needing these for OpenHarmony 3.1 builds.

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>

Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com>