Scheduled builds will allow us to re-test what's in HEAD without opening
a pull request. Making drafts start in manual mode will conserve
resources without limiting one's ability to iterate on selective
targets.

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

Include the machines-and-flavours file explicitly, from the local
repository.  It is already included via the build-generic.yaml
project-include above, but including it again here allows GitLab to pick
up the changes to the definition straight away. The include done via the
manifest repository is using the default branch, so it cannot pick up
changes to this file as it is being modified by incoming branches.

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>

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@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>

The manifest repository now offers new hidden jobs, that make
customization and reuse easier. Those allow us to remove bulk of the
custom logic, again, reducing everything to mere configuration.

The build-docs and update-docs jobs are entirely replaced by .build-docs
and .aggregate-docs (name change without logic change).

Custom .build job is split into smaller changes to the .workspace and
.bitbake-workspace jobs. Lastly, the variable OHOS_CI_GIT_REPO_PATH
is no longer relative to sources/ but includes it explicitly.

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

There are two separate issues here:

- CI_BRANCH_NAME doesn't exist, we want CI_COMMIT_BRANCH instead.
- The rules engine doesn't handle quotes in the normal sense.
Quotes are only allowed on literals, not variable references.

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

CI_BRANCH_NAME doesn't exist

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

The rules engine doesn't handle quotes in the normal sense.
Quotes are only allowed on literals, not variable references.

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

Set rule to run our build pipeline for git tags as well.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

When documentation changes, trigger the docs pipeline to update the
aggregated documentation view.

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

Zygmunt Krynicki authored 4 years ago and Andrei Gherzan committed 4 years ago

The implicit test stage is a scheduled to run after all the jobs from
the build stage succeed. This introduces a unneeded dependency between
building the code and building the documentation.

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

The manifest repository no longer contains distinct default.xml and
develop.xml manifest files. That role has been delegated to distinct git
branches.

Switch to the default manifest so that the deprecated compatibility
module which has the same effect, can be removed.

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

It seems that `**` matches only the directory parts, `*` is needed to
match files contained therein.

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

CI process in the meta-ohos repository is rather heavy, with large
number of long-running build jobs. The pipeline system allows
restricting job startup to a set of rules, and to further restrict each
rule to trigger only when one of a set of given files is modified.

This should allow efficient modification pipeline that only touches the
documentation or the meta-layers, without needlessly running unrelated
testing.

This is documented at https://docs.gitlab.com/ee/ci/yaml/#ruleschanges

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


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

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

With the improved .workspace and .build jobs merged into the manifest
repository [1], we can now set OHOS_CI_GIT_REPO_PATH and remove the
custom code that was necessary to implement this functionality before.

[1] https://git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/53



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

This further reduces some copying by including build-generic.yaml from
the manifest repository. Bulk of the logic is reused now, with the
switch to a custom branch of the meta-ohos git repository being the sole
exception.

One small optimization, that is also applied to the manifest repository
is the override to drop image artifacts. Since those are not needed yet
we can save the cost of performing the uploads to GitLab object storage.

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

This drops the local definitions of all the build flavours and all the
targets based on "develop.xml". This significantly simplifies this
pipeline and reduces duplication of the set of supported targets.

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

- Use re-usable .workspace job from pipelines repository
- Less repetition with more targets supported
- Higher uniformity with the pipeline at the manifest repository.

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


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

Zygmunt Krynicki authored 4 years ago and Andrei Gherzan committed 4 years ago

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

This fixes:

    $ test "$ACCEPT_FSL_EULA" -eq 1 && echo 'ACCEPT_FSL_EULA = "1"' >> conf/local.conf
    /usr/bin/bash: line 155: test: : integer expression expected

To avoid the problem and reduce complexity, move the Freescale-specific
logic to the only build that requires it.

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

Following documentation from
https://git.ostc-eu.org/OSTC/infrastructure/pipelines/-/blob/main/reuse.yaml
Add the reuse job which can fail, since this repository is not compliant
with REUSE yet.

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


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

Signed-off-by: Ettore Chimenti <ettore.chimenti@seco.com>

Stefan observed that CI job initializes bitbake with layer configuration
from the layer as checked out by git-repo, and only then switches to the
branch being tested.

This resulted in bitbake incorrectly failing to notice a layer that was
added by the tested patch.

The solution is to move all of the bitbake initialization stage from the
.build jobs "script_before" section, to the "script" section. In effect
any derivative job can use "script_before" to freely alter the source
tree before bitbake is initialized. Due to the lucky arrangement of YAML
anchors, the .build job's "script" keeps running with bitbake
environment sourced, so it can do exactly what one would expect - build
the desired recipe.

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

We have notced that some of ACTS dependencies do not build correctly for
Avenger96. This went unnoticed because the CI system is building the
plain image, that does not include any test dependencies.

Fix that by building the test image instead of the plain image, for
targets based on Linux.

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

Zygmunt Krynicki authored 4 years ago and Zygmunt Krynicki committed 4 years ago

This experimental pipeline performs bitbake builds in response to
changes proposed for the layers contained in the meta-ohos repository.

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