Walter Lozano authored 1 month ago and Dylan Aïssi committed 1 month ago

Since flathub does not support armhf anymore, avoid using it to make our
pipelines green. A proper solution will be to build and publish our own
version of rhythmbox3.

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

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

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

Fix the link to the repositories as it was supported by some redirections
that were disabled.

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

Otherwise pipelines triggered on other branches will overwrite
apertis-oslist-daily.json leading to list images for old
apertis releases instead of the current dev release.

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

In 62a8cd04 we increased the size of the
boot partition on the RPi4 to ensure that there is enough space to store
at least two versions of the kernel. However this was only done for
standard apt images as ostree images use ostree-image-rpi64.yaml rather
than image-rpi64.yaml.

Repeat this partition size change for the OSTree images as well as we
are still seeing failing upgrade tests with the following error message:

May 19 02:13:03 apertis apertis-update-[1029]: Ostree upgrade failed: Installing kernel: regfile copy: No space left on device

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Detlev Casanova authored 1 year ago and Walter Lozano committed 10 months ago

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

To align with what is done in ospack-hmi move the step to overlays before
the step to add new repos.

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

The image recipes include dpkg-excludes to avoid installing documentation
for target image. However, this only is applied after the bootstrap process
causing some documents to remain in the rootfs.

A partial clean up is done on the last steps of the image generation, erasing
/usr/share/doc/*, but there are other places for documents.

Clean up all the folders that are mentioned in dpkg exclusions after the
bootstrap to save space and to ensure that SBOM which does not support
autogenerated files, like man pages, is accurate.

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

The boot partition is used to stored the Linux kernel, and should be enough
to store at least two versions of it, for instance, to allow OSTree upgrades.

By default Apertis images uses 256 MB for this partition, but in RPi4 this
pattern was not followed due to the presence of the firmware partition. Under
this sceario OSTree tests might fail with the error:

Feb 22 05:19:24 apertis apertis-update-[1058]: Ostree upgrade failed: Installing kernel: regfile copy: No space left on device

In order to keep the same pattern as in other images extend this size moving
all the other partitions.

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

The version of ostree-push in v2023 does not support  the -o option. The
port is provided by the crafted 'ssh' command variable instead.

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Pablo Vigo Mas authored 1 year ago and Ritesh Raj Sarraf committed 1 year ago

The SSH server on the Aurora system, operating on port 22, is consistently under probing attempts by attackers. Enhancing security on the server can be achieved by transitioning to port 7711.
Pipeline is now configured to use the new SSH port of the Aurora server.

Signed-off-by: Pablo Vigo <pvigo@collabora.com>

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

Vehicle daemon provides the interfaces for application to develop the
appby using real world vehicle data.
-	Listing all the connected sensor and actuator to the device
-	Subscribe any specific vehicle data
-	Monitor all the vehicle data
-	Mock backend to simulate all the data

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

During the bootstrap process only target repository is used, which provides
alternative packages like busybox-gzip instead of gzip due to licensing
issues. However, non target images requires the full version of them to
allow development work.

Add gzip to the list of packages to replace to allow development work.

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

Avoid cloning archived project helloworld-webapp as it is not longer
supported.

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

Script clone-sample-repos is aimed to clone the sample repos in the SDK,
however, it does not properly point the branch that should be used as
it does not take into account the distribution id.

Fix the issue by properly point to the branch name.

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

Martyn Welch authored 1 year ago and Walter Lozano committed 1 year ago

The action run to generate the ova image isn't currently marked as a
postprocess task, so it's being run when the image is still mounted.
This has oddly seems to be working in most places, that is until it
stopped in a teams use of this recipe resulting in missing boot config
files.

Mark this action as a postprocess step to avoid racy behaviour.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Due to changes in priorities we no longer support Kanto and given the
IoT image is essentially a fixedfunction image with Kanto support
on top, let's drop it.

This also drops cloud2edge setup support which is used only by IoT
image tests.

Signed-off-by: Andre Moreira Magalhaes <andre.magalhaes@collabora.com>

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

This enables tests for the IoT image, as well as setting up and bringing
down the needed setup steps on our cloud2edge instance.

https://phabricator.apertis.org/T8949



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

The rk3399 image recipe introduced a new `sbc` (single-board computer)
variable for selecting the target device.

We now build the rk3399 image recipe for different target `sbc`. In
order to differentiate between the output images, the `sbc` variable (if
defined) needs to be appended to the image name.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

The rk3399 image recipe introduced a new `sbc` (single-board computer)
variable for selecting the target device. This variable needs to be
passed to the debos recipe as a template variable.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Christopher Obbard authored 2 years ago and Ariel D'Alessandro committed 2 years ago

If building images in a different artifactdir from the recipedir,
for instance:
  $ debos --artifactdir=out image-uboot.yaml

the postprocessing steps which compress the images fail.

Fix the postprocessing step to save the resultant artifacts inside
the artifactdir rather than assuming the current directory is where
the artifacts should be saved.

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Since we have support for this board in Apertis u-boot and kernel package,
build the apt-iot and apt-fixedfunction images for this board: the same
images which we build for the rock-pi-4 board.

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

The RPi loader tries to load dtbs and overlays for u-boot from the
firmware partition. Currently, this recipe is only copying the dtb files
from u-boot, not overlays.

The CANOPi board requires the VL805 overlay in order to properly
initialize the USB controller, otherwise it will hang during boot.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

The UP Squared 6000 board fails to bring up audio as it tries to load
the SOF firmware that is signed with the community key.

Starting from Linux v5.16, the following patch is included:

  commit 405e52f412b85b581899f5e1b82d25a7c8959d89 (bad)
  Author: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>

      ASoC: SOF: sof-pci-dev: use community key on all Up boards
  ---
   sound/soc/sof/sof-pci-dev.c | 10 +---------
   1 file changed, 1 insertion(+), 9 deletions(-)

Although the community key is the preferred option to allow developers
to sign their own firmware, the Skylake found in the UP Squared 6000
board only supports firmware signed with the production key.

Fix this by adding the module option (snd-sof-pci.fw_path="intel/sof")
to the kernel cmdline arguments, so the right firmware is picked up.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Commit 717dda2c ("image-rpi64: Install rpi64-autoconfig-connman package")
installed the rpi64-autoconfig-connman package on rpi64 recipes.
However, it missed the required overlay so connman enables wifi by
default.

Note that original purpose of this feature is to allow users to
configure the system wifi on a headless system without even a shell.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

The RPi loader tries to load a dtb for u-boot from the firmware
partition. Currently, the apertis-image-recipes recipes for RPi are
copying these dtb files from the kernel.

It makes more sense to copy these dtb blobs from u-boot rather than the
kernel, as the bootloader is the one using them. Moreover, these dtbs
are built supporting overlays, which we might use for the CANOPi
auto-detection support.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

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

Edmund Smith authored 2 years ago and Sjoerd Simons committed 2 years ago

In the previous commit we switched from using "submit" and "monitor"
to using "generate" and "run". This moves the template files to fit
that naming pattern too.

Edmund Smith authored 2 years ago and Sjoerd Simons committed 2 years ago

We're no longer submitting jobs in the submit step, nor are we
monitoring jobs in the monitor step. This is only a separate commit
from the actual technical changes to make the earlier commit easier
to follow. This is just mechanical renaming of:

- submit -> generate
- monitor -> run

The actual files will be renamed in the next commit to make the
diffs cleaner and easier to follow.

Edmund Smith authored 2 years ago and Sjoerd Simons committed 2 years ago

This matches the changes to the apertis-test-cases repo. Previously we
had a two stage process for Lava tests of:

- generate and submit
- monitor

for each set of test cases. This is a restrictive setup, because it is
impossible to use CI_JOB_TOKEN within the lava jobs themselves
(because the token expires on completion of the submission job, before
the lava job itself may even have started).

The new model is simply:

- generate tests and pipeline
- Run each test in its own job in the generated pipeline

That means we still have pairs of jobs at the top level, one job to
generate the tests, as before, which now also generates a pipeline;
the second job is a trigger job which executes the pipeline, bringing
in the generated tests.

One of the challenges in the BOM generation is to pick the correct license
and copyright information for a source file, due to:
- Copyright reports use wildcards
- Source files are obtain from debug information with not reliable path
  information.

To overcome this issues improve the generation by:
- Evaluate the trickiness of the debug information (unit)
- In case of a high level of trickiness only trust in copyright reports
  without wildcards (full report)

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

In order to provide a more reliable path prefix and have additional
information regarding it, improve its calculation

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

In order to have a clear code do a little rework, by creating more
general functions.

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

This service is failing on the UP Squared 6000 board, causing the sanity
check LAVA test to constantly fail.

This seems to be an issue on the asus-nb-wmi driver not being able to
drive the brightness properly on this device.

As the kbd-backlight is not really a requirement, let's disable this
service temporarily on Apertis.

apertis-issues#163



Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Detlev Casanova authored 2 years ago and Ariel D'Alessandro committed 2 years ago

This packages is very conveniant for PI 4 users, because they can
enable Wifi without serial console or wired Ethernet connection.

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

The /etc/os-release file is edited in the chroot environment (chroot: true),
but that chroot env cannot be accessed after the "Reset rootfs before
deploying OSTree" step (chroot is failing because /etc/resolv.conf is
missing)

It also makes sense to edit /etc/os-release before running the "OSTree
commit" step to include the correct /etc/os-release in the ostree commit.
So the editing of /etc/os-release ("Customize image version metadata"
step) is moved right before that.

Fixes: apertis-issues#31
Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>