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

--

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

CI: Remove build for dual espresso again

The pipeline is not setup to build from different manifest and so on,
and the dual_espresso manifest will probably go to a seperate repo
to keep it private.

--

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

CI: Remove '--verbose' from deploy step

--

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

manifest: Added manifest file selection to ci-test

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1285aad7

manifest: Added manifest file name to integration script

BCS 746-000518

--

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

build: Added DualEspresso

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0941262a

layers: Added nogplv3 and dual-espresso layer to CI/CD

--

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

CI:package_release: Remove "GUF-" prefix from gitlab artifacts dir

BCS 746-000637

--

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

manifest-CI: Refactor manifest pipeline files

* Split up build and package steps in separate files
* Add additional comments
* Add log output

BCS 746-000637

--

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

Fix remote name on retrigger stage

--

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

Move repositories to git.seco.com

Rename variable JENKINSGUF_SSH_PRIVATE_KEY / SSH_PRIVATE_KEY to
GITLAB_PRIVATE_KEY on this occasion, because it contains a private key
that was generated exclusively for this use case. The according public
key has been added as a deploy key in GitLab to all repositories that
this repository needs access to.

Add more detailed documentation concerning this configurationdirectly in
the gitlab-ci files.

--

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

manifest: check if docker build folder is empty

BCS DevOps-000035

--

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

CI: integrate_into_manifest: Fix integration for recipes in SRCREV file

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@976aaec9

CI: deploy_gitlab_ci: Fix merge, integration branch was used after delete

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@65c6f273

CI: Rename foobar to ci-test, like the job names

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@60c311ab

CI: Reuse existing integration branch preserving manual changes

--

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

CI: integrate_into_manifest: Fix bug introduced when splitting functions

--

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

CI: disable 'check' job for gitlab-ci integration as integrate is already disabled

--

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

CI: Enable MR pipeline for integration of gitlab-ci again

Our settings refuse to merge if no pipeline has been run.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@69d604a4

CI: Fix merge pipeline

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@31d6d7da

CI: deploy_gitlab_ci: Rework the deployment of gitlab-ci into the child projects

The deploy_gitlab_ci now creates the integration commit and branch in
each passed subproject and create an integration commit in the manifest
containing all these new revisions.
A build is then triggered on this commit to test the functionality.

Split the update_submodule functions to reuse them in different ways.
Remove some previously used files.

BCS 746-000740

The "initial-draft" branch is deprecated. Use the branch "master"
instead. Currently this should not change the content.

According to our company licensing policy for software the Yocto layers
should be licensed under the Apache 2.0 license.
Adapt the LICENSE-2.0.txt file from https://www.apache.org/licenses/LICENSE-2.0.txt
as described in the APPENDIX.

Add the license as LICENSE.txt file to the layer repository.

BCS 746-000657

Since version 1.36.2, the NetworkManager is build with Vala support.
We don't include Vala in our Image and disable it therefore.

The standard image was missing the GPLv3 packages.
Added them back in and created a new distro without GPLv3.

The script was relying in the /dev/input/touchscreen link which was not
available in FNGSystem previous to version 16.
This fix now loops though all available devices and takes the first
device with absolute axis.

The FEATURE_PACKGES directive doesn't work here, because the
packagegroups aren't run like a normal recipe.
Moved the GPLv3 packages back to PACKAGES for normal inclusion.

Contains the regular sans fonts plus the Chinese (simplified and traditional),
Japanese, Korean, and Thai glyphs.

BCS 746-000525

The automounting can now be enabled/disabled via the PACKAGECONFIG.

BCS 746-000742

BCS 746-000518

The image feature needs to be set separately.
See comment in guf-image.inc and gplv3.bbclass.

BCS 746-000741

- Updated general packagegroup info
- Moved all GPLv3 software to own overload. The software now needs to be
activated explicitly via the gplv3 image feature.