These jobs are no longer used here, now they live in the
apertis-image-recipes repository. Keeping them here is
more confusing than useful.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

These tests will be used to test RPi64 images on LAVA

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Apertis v2022 is not supported anymore, instead
use the last release of Apertis v2023.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

To avoid repeating settings from image recipes, use a tiny Python script
to parse the original pipeline’s YAML definition and collect variables
into .env files to be sourced directly into the image building job’s
shell.

The original pipeline places the devroot tarball in a directory that
would otherwise not be accessible in this job, so we override it by
passing another -t devrootpack: argument to debos.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

The image building jobs are made dependencies of test jobs in order to
allow them to use freshly build image artifacts. The dependency is
marked optional to allow the pipeline to run with daily images as
before when build-custom-image: yes is not set for the package.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

While BUILD_RESULTS_URL refers to the artifact from the obs-capture job,
SOURCE_RESULTS_URL refers to the artifact from the build-source job.
To avoid capturing duplicated files on gitlab side, the debian source
package will no longer be captured by obs-capture since it's already
captured by build-source.

Moreover, for native packages, SOURCE_RESULTS_URL refers to the main
tarball instead of the *.debian.tar.* tarball which doesn't exist for
native package.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

Use lava-runner templating to pass package name instead of hardcoding it with generate*jobs.py scripts

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

To be consistent with the LAVA job which retrieve artifacts by
passing CI_JOB_TOKEN in header of curl request.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Andrej Shadura committed 1 year ago

In order to retrieve artifacts from private gitlab projects,
we need to pass the gitlab CI_JOB_TOKEN as header to curl
otherwise access is not granted.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Nithin Mysore Nagesh authored 1 year ago and Ritesh Raj Sarraf committed 1 year ago

Modify the steps to run the test on SDK and enable nested virtualization
as part of pre-condition.

Signed-off-by: MN Nithin <MN.Nithin@in.bosch.com>

This option is required to trigger the test pipeline as a child pipeline
in our ci-package-builder pipeline. Without 'rules: when' set
the child test pipeline is not triggered.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This is useful to get a nice summary from the GitLab webui.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This feature will be used for package centric jobs, since we want to use
includes defined in tests/apertis-test-cases whereas the jobs run in
another repositories (i.e. pkg/***).

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This script is used by package centric jobs to get
the artefacts URL to retrieve from the target device.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
Signed-off-by: Malik Mlitat <malik.mlitat@de.bosch.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>
Signed-off-by: Malik Mlitat <malik.mlitat@de.bosch.com>

This option allows to select which test type to generate.
This is useful for package centric jobs since we want to generate
jobs only for the type "package".

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Nithin Mysore Nagesh authored 1 year ago and Ritesh Raj Sarraf committed 1 year ago

Create separate job to validate vehicle daemon functionality on target

Signed-off-by: MN Nithin <MN.Nithin@in.bosch.com>

Signed-off-by: MN Nithin <MN.Nithin@in.bosch.com>

Tiny containers test consist in flashing a stable Apertis release and on
top of it download and test the tiny container of the release under test.
After switching the stable release to v2023.3 to support the new R-Car
board a failure is observerd due to missing dd.

In v2023, rust-coreutils is the replacement for coreutils, however, the
support of dd is disabled as it was still experimental and the replacement
chosen was busybox dd.

In order to fix the issue, switch to busybox dd to run the test.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Nithin Mysore Nagesh authored 1 year ago and Walter Lozano committed 1 year ago

- Add group entry: Group entry was missing due to which jobs were not
  generated for rhosydd.

- Modify image-types: Since this test executes unit test cases and
  uses devscripts which is available in development repository, this
should be run only on sdk and basesdk. Separate test to be implemented
for target.

- Add dependencies

Signed-off-by: MN Nithin <MN.Nithin@in.bosch.com>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Walter Lozano authored 1 year ago and Sjoerd Simons committed 1 year ago

During the branching the NFS URL for R-Car was tweaked, causing the tests
to fail. Fix the NFS URL.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Siva Krishna Prasad Chinthalapudi authored 1 year ago and Walter Lozano committed 1 year ago

add step to install `xserver-xephyr` pkg explicitly

Signed-off-by: SivaKrishnaPrasad <sivakrishnaprasad.chinthalapudi@in.bosch.com>

Following the same approach used at image generation, disable HTTP 2 in
flatpak to overcome connections issues as OSTree does not support retries.

infrastructure/apertis-image-recipes!612
https://github.com/ostreedev/ostree/issues/2570
infrastructure/apertis-issues#436



Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

With apertis-dev-tools 0.2023.4, a new mandatory flag was added
for sdk-import-debian-package. This new flag allows to pass the reason
for importing the package. See commit 1588bc10 in `pkg/apertis-dev-tools`

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

`aa-status` was merged back in `apparmor` in 3d5b5245
during the bookworm rebase because the reason of the split was no
longer valid.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Walter Lozano authored 1 year ago and Ryan Gonzalez committed 1 year ago

After relaxing hmi-switch-graphical-applications to use any application
some instructions were not properly updated. Update the test case to
be coherent with the new approach.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Switch to the new R-Car r8a779m1-ulcb device type as it is the new
reference board for this release.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

telepathy is no longer used for testing and not available in
Apertis since the Bookworm rebase.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

The test hmi-switch-graphical-applications requests to open Fonts application
which is installed by default in HMI images via Flatpak, but not installed
on SDK. Since the test can be run with any graphical application, relax
it and mention Fonts only as a suggestion.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Sudarshan C P <sudarshan.cp2@in.bosch.com>

This test is expected to be run on a system with its rootfs on an eMMC storage
and not on a USB device. Using a rootfs from a USB device can lead to
failures like the systemd service 'usbmount@dev-sda1.service' failing to
start since /dev/sda1 is already mounted at /boot/efi.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>