When switching from scheme 1 to 2, there was a bug leading to an
unformated partition.

Additionally I removed the partition message for FT2. This is only
used during the yocto installation and was in the wrong position
anyway.

The implmentation was not really working when used in a yocto
installation, as it would have needed a relocation of FNGSystem.
Now the explicit change of the partition scheme is only be possible
together with the installation of FNGSystem.

When FNGSystem 15.1 was just installed and only one partition was
setup on the device the installation failed.
This is fixed here.

Also: in A-B installation mode is the used target (A or B) reported
after the installation.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b2bc220

Define yamllint job explicitly in each pipeline

The yamllint job was included in the pipeline implicitly via the
inclusion of common.yml. This is not very transparent. Make the common
definition a base job and extend it explicitly in each pipeline now.

Add infrastructure stage comment header into both yaml files.

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@686323c6

Remove yaml redundancies in manifest-integration

Leave all common yaml parts in manifest-integration.yml and add
manifest-integration-yocto.yml and manifest-integration-ci-test.yml
containing the different variable assignments for each environment.

The repos including these files have to be updated with the new names.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c751096

Harmonize manifest-integration yaml files for yocto and ci-test

This is the first step for reducing code duplicates.

BCS 746-000807

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c877f9c9

retrigger: Allow to specify the manifest's remote identifier in a variable

Costum manifest may override this variable

The nfs-statd systemd service is disabled by default.

BCS 746-000876

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@d9660a80

build-jobs.jinja2: Specify master branch variable again

If the MASTER_BRANCH_MANIFEST variable is set in the manifest's
.gitlab-ci.yml file, it may not find its way to the generated job,
if it is not explicitly set during generation.
That is done with this patch.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2e6c1b4f

Build jobs: Use parent-child jobs to generate needed build jobs

* Move all build, deploy and test stubs to the manifest-build.yml
* Create a new job to generate and trigger the build jobs dynamically
* Add the base jinja2 file for the build jobs.
* Add initial docs for the manifest pipeline
* Remove unused files

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5

Move python scripts to subfolder

BCS 746-000808

For imx8m it is necessary to specify drm device 0 to run the qt-compositor
with eglfs backend.

BCS 746-000787

This allows us to draw the progress bar directly on top of the kernel
splash logo. By default, psplash only displays the progress bar.

BCS 746-000786

Normally we would use network-manager, but for the gplv3 free variants
it is not available. In these cases we keep systemd-networkd as
network tools available.
Also adapt the call to gf-network-conf in the postinsts step during the
first boot to automatically determine the used network tooling.
This way the configuration for systemd-networkd is generated from the
xml setting as needed.

Until now the MACAdress was not configured if systemd-networkd was used.
Now the MACAddress is added to the newwork config file like it is done
when network-manager is used.

The weston-start script for xwayland overrides the module loading of the
notify library. Without notify, Weston doesn't report a successful start
back so systemd. As a result, systemd stops Weston after hitting the
timeout period.

Without the module loading directive in the start script, xwayland needs
to be activated in the weston.ini.

The nogplv3 distro now includes the default guf-wayland distro
and only removes the gplv3 distro feature.

If x11 and wayland are both activated in the DISTRO_FEATURES, we add
xwayland and its xserver implementation to the image.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6980d48

Update meta-seconorth-dual-espresso path

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@83002e07

accept_merge_request: explicitly check if MR has merge conflicts

According to the documentation [1] we should get a 406 error from the
API if we try to merge a merge request which has a merge conflict. We
are experiencing a different behaviour, though, where we are getting a
405 error in this case. There is an open GitLab issue on this topic [2].

In our error handling we assumed that the reason for a 405 error is most
likely a required pipeline which is still running. This assumtion,
however, leads to wrong behaviour in cases where no pipeline is started
at all.

Fixing this now by explicitly checking for merge conflicts at the very
beginning of the error handling sequence.

[1]: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request
[2]: https://gitlab.com/gitlab-org/gitlab/-/issues/364102

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d

Document "skip build" label

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e514076

Add possibility to skip MR pipeline check via label

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ee151673

Add possibility to skip MR pipeline build via label

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ad9d367e

Allow check job to fail

This makes merging a project MR possible even if the manifest has
received new commits since the MR pipeline build has run. The developer
is responsible for deciding whether it is safe to merge it without
having a build based on the latest manifest.

BCS 746-000794

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@81c2ad85

merge_into_manifest: fix error message if MR already exists

The tools recipes still use SSH as protocol for the checkout.
Since we have opend our repository to the public, SSH isn't available
anymore. Because of this, we switch to HTTPS as protocol.

Felix Gerking authored 2 years ago and Jonas Höppner committed 2 years ago

imx6ull uses the linuxfb backend,
imx6 and imx8m* using eglfs.

Felix Gerking authored 2 years ago and Jonas Höppner committed 2 years ago

The qt-multi-screen-compositor is based on examples from QT
to implement a compositor based on QtWaylandCOmpositor.
The implementation is done mostly in qml.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6fbbf338

CI: Add fake lava test to ci-test, reduce fetch depth in update submodule

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@d820110c

CI: Add variable containing the port for ssh access of the gitlab instance

Our server installation uses port 4444 for ssh access. The lava tests
didn't took this into account.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@a06956de

Rename layers to seconorth

We have now platforms with custom rootfs names in the config.
It is easier to install if the correct name is already in the
install script.
With this change, the image name for the install script can be
adapted in a bbappend file.

Add section for the license into the README.md.

BCS 746-000657
BCS 746-000659
BCS 746-000780

To find the touch the capabilities entries in the sysfs are checked.
On Nallino the format contained a space, which made the script exit
with error. This change now (hopefully) decodes it correctly.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@67b0195a

CI: Increase infrastructure timeout to 10min

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d2210b6

CI: deploy-gitlab-ci: Don't stop integration when one project is already updated

Prior to this change the integration stop when one of the projects had
already the latest ref of gitlab-ci in to submodule.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f09c66c

CI: deploy-gitlab-ci: Don't stop integration when one project is already updated

Prior to this change the integration stop when one of the
projects had already the latest ref of gitlab-ci in to submodule.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c39166f

CI: deploy-gitlab-ci: Don't stop integration when one project is already updated

Prior to this change the integration stop when one of the projects had
already the latest ref of gitlab-ci in to submodule.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@aaac8d1c

changelog_generator: Use logging instead of print, fix black

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@79afb233

CI: Move changelog_generator to gitlab-ci project

The script can also be run in the normal python container, so this
slightly reduces the complexity.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@383a5aca

Added qt-multi-screen-compositor to project list

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e88ad8e

buildfng: Moved the image and distro variables to global

The image and distro for the buildfng job can now be set via
global/external variables.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@751fc360

Improve CI documentation

BCS 746-000636

The framebuffer could be accessed by a simple write the the /dev/fb0.
This tool allows similar access by piping the data into it and
specifying the connector as parameter.
It also allows to query few things from the drm.

The recipe has a GPLv3 licenses and needs therefore to be moved to the
GPLv3 subgroup.

Previously, iptables was only included via dependencies.

The install script backups some variables from the existing u-boot
environment before overwriting it. This failed for devices where no
environment was available yet, which lead to stop the update with error.
This case is now ignored and the installation continues without backup
in this case.

Rename the distribution to SECO Northern Europe distribution and
reference the manifest as the main source of information.

BCS 746-000659

We borrow some recipes form public layers. However, most of the public
layers are licensed under the MIT license. To make the licenses clear
copy the corresponding license files into the relevant directories next
to the recipe in question.

Recipes in question:
- rtl8812au
- kbd
- beep
- mxt-app

BCS 746-000658

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@bcb6076b

CI: Add check if integration branch is on top of target branch before reusing it

The integration branch was reused even if there where new commits on the
target branch, which could lead into reverting some changes.
This adds a check, if the existing integration branch is directly based
on the target branch and deletes it if not.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0

CI: Pull new changelog_generator image, add token to the call.

BCS 746-000785

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0

Update README.md: Add description on the gitlab-ci CI and how to deploy

This reverts commit 14784648.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0

CI: Pull new changelog_generator image, add token to the call.

BCS 746-000785

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0

Update README.md: Add description on the gitlab-ci CI and how to deploy