Using build job name to download bundles doesn't work. We need to introduce
new var and make it mandatory for lava jobs containing the `sysota`
in job name.

Signed-off-by: Stevan Radaković <stevan.radakovic@linaro.org>

This reverts commit a180a4b8.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Artem Kondratiuk authored 2 years ago and Pawel Stankiewicz committed 2 years ago

Signed-off-by: artem.kondratiuk <artem.kondratiuk@huawei.com>

These will, as other LAVA jobs, end up in SQUAD and, consequently,
in LAVA. It's basic tests on QEMU, running `rauc status` and `rauc
install bundle` commands and validating output.

Signed-off-by: Stevan Radaković <stevan.radakovic@linaro.org>

Chase Qi authored 2 years ago and Stefan Schmidt committed 2 years ago

Check the current version with `bitbake -s` and the last tested version
via squad's api. When version is changed, continue the following tests,
otherwise, skip the tests.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Chase Qi authored 2 years ago and Stefan Schmidt committed 2 years ago

gcc test suite has been integrated in oe-selftest framework. It allows
to run gcc test against qemu vm and within the build env using qemu
linux-user mode.

These tests can be run in gitlab CI with qemu friendly runners. This
commit add three oe-selftest jobs to run the tests using qemu
linux-user, qemu x86-64 vm and qemu arm64 vm.

Test log and sum files are collected as job artifacts.

When all test jobs finish, report job will be triggered to parse the
sum files to generate results in the format that supported by squad. The
report job will upload results to squad for reporting.

Closes issues #8 and #9.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Given test scope for new MRs is not defined yet and we only have one
rpi4, b68 and c61 in the warsaw lab which are occupied mostly by daily
scheduled pipeline, starting with boot and smoke tests on qemu devices
should be a good starting point for per MR testing.

Jobs that extend `.lava-test` will be added to MR's pipeline and
schedueld pipeline.

`.lava-test-scheduled` extends `.lava-test` with new scheduled pipeline
only rule. Long run jobs like ltp should extends the job so that they
wouldn't prevent MRs from merging.

Solves #486.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Unqualified jobs, which rely on the default compiler, are gone.
Qualified jobs explicitly configure either clang or gcc and use the
appropriate suffix. Qualified jobs have needs/depends set to empty to
both avoid waiting for previous stages to start and to avoid pulling in
artifacts from the previous stage.

Qualified jobs inhabit two new lanes: build-gcc and build-clang, to
visually break the already long column of "build" jobs.

Job ordering within a lane is not exactly matching, gcc-clang. This is
noticeable with the jobs using the "extra" suffix. The reason for this
is unclear.

Some jobs are marked as broken as they do not build with clang. Allow
them to fail and make them start manually until more patches arrive.

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

This is workaround for eclipse/oniro-core/oniro#574


Currently changes which are not covered by this condition triggers
invalid yaml . We will optimize it later

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

Add jobs to build and publish update bundles for qemu - both x86 and
x86_64

Signed-off-by: Stevan Radaković <stevan.radakovic@linaro.org>

When looking at pipeline [1] we have realized that the newly introduced
bundle build and publishing jobs pose a problem for unrelated updates
of the tree, as depending on which exact files are modified by the
incoming pull request, the build jobs may not spawn, causing a
dependency error on the bundle and publishing jobs.

When initially introduced, it was overlooked that the jobs both have a
dependency on one another (build->bundle->publish) *and* come with a
distinct set of rules that govern if a specific job is created in a
given pipeline.

To resolve the problem move the rules to a new dot-job, called
.workspace-rules, and inject the dependency on .workspace-rules to all
the jobs that share the dependency chain.

[1] https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/pipelines/4285



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

Chase Qi authored 2 years ago and Stevan Radaković committed 2 years ago

Signed-off-by: Chase Qi <chase.qi@linaro.org>

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

This expands automatic updates to the SECO B68 board. Both new jobs
re-use existing generic jobs and contain no new logic.

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

The HawkBit instance needs to be configured externally and reachable
from the runner performing the publishing step. The location of the
instance must be provided through environment variables compatible with
hawkbitctl, namely HAWKBIT_{URL,USERNAME,PASSWORD}. HAWKBIT_TENANT is
optional and untested.

The bundle is added as an artifact to a new software module named after
the bundle, using bundle timestamp as the version. The module is then
placed in a distribution named after the image (not the bundle), with
the exact same version.

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

This allows the bundle job to be started even if just one of the jobs
in the previous stage, the one for pi4 image build, succeeds. This is
better for testing and allows jobs to start and finish faster, reducing
total build time.

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

Enable smoke, ltp, kselftest and perf tests on seco-c61.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Chase Qi authored 2 years ago and Andrei Gherzan committed 2 years ago

Signed-off-by: Chase Qi <chase.qi@linaro.org>

The EF infrastructure (GitLab) doesn't support image registry. This
moves the CI logic of building and deploying all the container images to
the OSTC instance while EF catches up[1].

[1] eclipsefdn/helpdesk#1108



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

Chase Qi authored 3 years ago and Stevan Radaković committed 3 years ago

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Set lava-test and lava-report job as scheduled pipeline only for the
below reasons.

* lava-test requires token set using GitLab variable for job submission
* lava-report depends on all test jobs

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Zygmunt Krynicki authored 3 years ago and Stefan Schmidt committed 3 years ago

The update bundle is built with the new hidden job .build-rauc-bundle.
The job is documented and instantiated in the main pipeline.

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

Signed-off-by: Chase Qi <chase.qi@linaro.org>

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

Signed-off-by: Chase Qi <chase.qi@linaro.org>

The 'when: never' rule should be put on the top to prevent gitlab from
adding the job to pipeline.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Chase Qi authored 3 years ago and Stevan Radaković committed 3 years ago

Signed-off-by: Chase Qi <chase.qi@linaro.org>

This closes: #226

Signed-off-by: Chase Qi <chase.qi@linaro.org>

lava-test badge shows success rate for on device testing in lava.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Introduce machine variable for lava-test and search build images for the
test target device only to make sure only images for the target device
submitted for test.

This closes #215.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Chase Qi authored 3 years ago and Stevan Radaković committed 3 years ago

Signed-off-by: Chase Qi <chase.qi@linaro.org>

After all test jobs for a pipeline finish, trigger lava-report via gitlab api
to collect test results from all jobs.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

* fix the syntax for CI/CD var check
* enable lava report

Signed-off-by: Chase Qi <chase.qi@linaro.org>

CI_LAVA_TOKEN is required for submitting job to LAVA server. It should
be set in instance level gitlab CI/CD variables for testing forking dev
flow based MRs.

With `when: never` rule, test job will not be added to pipeline if the
above var not set. If the condition not set in test job that extends
`.lava-test`, `.lava-test` will ask user to do so and then exit with
unsuccessful job status. There is no easy way to exit early with
successful status yet. See
https://gitlab.com/gitlab-org/gitlab/-/issues/329217#note_572963049



Adding the above condition in `.lava-test` has no impact on test job
that extends the `.lava-test`.

Signed-off-by: Chase Qi <chase.qi@linaro.org>

Signed-off-by: Chase Qi <chase.qi@linaro.org>

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

This may be reverted ASAP,
this change was suggested by @zyga to suspend bot failures
on release

Cc: @zyga
Forwarded: https://booting.oniroproject.org/distro/oniro/-/merge_requests/383


Signed-off-by: Philippe Coval <philippe.coval@huawei.com>