--

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

deploy_gitlab_ci: integrate only correct projects into the manifest

Previously we integrated all projects into the manifest, even those that
belonged to a different manifest branch. That led to all manifests
having the same project revisions, even if they should be different due
to different intgrated project branches.

Save a list of integration sources for each manifest branch separately
now, so that we can check which project belongs to which manifest branch
later.

--

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

Fix potential error message in retrigger job

TypeError: 'NoneType' object is not subscriptable
Example:
https://git.seco.com/seco-ne/yocto/infrastructure/ci-test/minimal-manifest/-/jobs/127610

--

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

Check if variable is defined before checking it value

--

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

Fix jinja2 "or" operator

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8da534ec

Run integration pipeline for target branch only

When we're integrating a single branch into a single manifest branch,
there is no need to run the intgeration pipeline for all configured
integrations, but only for those that match the target branch of the
current merge request.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8c94b725

ci-test: add job to check for correct foo branch

This should catch an error where during a gitlab-ci merge process the
wrong foo branch is integrated into the manifest, which happened in
Yocto.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@163c7e1e

Add yml extension to jinja2 templates

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@59523aa0

check job: disable verbose output

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@28bf0065

retrigger: add job states to log message

--

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

deploy_gitlab_ci: fix target branch in integration merge request

We need to pass the correct target branch to the merge request creation
instead of using the project's default branch.

--

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

Run yamllint job on gitlab-ci integrations

Otherwise no pipeline is created at all in these merge requests, which
prevents the MR from being merged.

--

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

changelog_generator: Fix machine project ID

We have deleted the original project due to git corruption. Replace with
the new project's ID.

--

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

deploy_gitlab_ci: fix project argument passing

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8a38f194

Put all manifest intgeration jobs into a single stage

--

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

deploy_gitlab_ci: explicitly pass gitlab-ci project and branch

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@172e7625

Improve error messages

--

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

Improve naming of functions and variables

--

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

Retrigger MRs from all integrating projects

Instead of getting the projects from the manifest file, search them via
their INTEGRATION variable.

Improve log messages on this occasion: print URL instead of just IDs.

--

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

Deploy gitlab-ci to multiple branches

Add different integration jobs for different manifest branches. The
merge stage only has one job for each manifest, though, because
otherwise we cannot guarantee a consistent state for all branches.

Extend the deploy script for this purpose, so that it can deploy to
multiple manifest branches at once.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@771dcff1

Fix temporary dir path

We were passing the complete TemporaryDirectory object to the repo clone
function instead of just the path string, resulting in the repo being
cloned into a local dir "<TemporaryDirectory '/tmp/tmphwakypf8'>".

Fix this to actually use the generated temp dir.

This change makes it necessary to keep the TemporaryDirectory object
reference until we don't need the directory anymore, otherwise it will
be removed immediately.

--

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

Print less important output in grey color

--

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

deploy_gitlab_ci: remove hard-coded integration targets

Get targets dynamically using the INTEGRATION variable instead.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@94cd6781

Recurse to child pipelines on retrigger

This makes it possible to retrigger jobs that are not part of the
given pipeline but in any nested child pipeline of it.

--

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

Ignore __pycache__ in scripts directory

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0c29c995

Refactoring: rename arguments for consistency

--

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

Remove hard coded project and branch variables

MANIFEST_PROJECT, MASTER_BRANCH_MANIFEST, MASTER_BRANCH_PROJECT

--

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

Add rules for integration pipeline

--

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

Improve log messages

--

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

commit_and_push: do not pass branch

Branch can be implicitly determined via the repo.

The workaround to exit the RTC detection if we're not on a Tanaro
was missing a exit.

The patch isn't needed anymore and throws an error during the build.
Remove it here until it is removed from meta-freescale.

The imxdma library doesn't compile on the i.MX6 right now.
Moved it to an i.MX8M only group.

The dynamic layer override for our i.MX8 devices has an extra
packagegroup. For the i.MX6 devices, this group isn't available
and leads to an error during the Yocto build.
Added a dummy group to prevent this error from happening.

The imxdmabuffer and imxvpuapi libraries have been added.
They can be used to test the VPU functionality and the allocation
of memory blocks.

BCS 746-000905

The imx-vpuwrap package was removed because the VPU support was broken
in Dunfell. Re-added the package to enable the VPU support in
Kirkstone.

The handling of custom devicetrees and devicetree overlays has changed.
Applied the changes made to the fng-install script to the fngsystem-
self-update script as well.

If no custom devicetree is set, the devicetree file isn't present.
In this case, the script would clear the default devicetree from
the boot config. Added a check to the script, that prevents the clearing
of the devicetree parameter.

The post-install wasn't handling the alternative boot configuration.
Also the combine step for kernel + devicetree was failing on i.MX8
devices because of space limitations.

The environmental variable based passing of devicetrees and overlays has
been replaced entirely by a file-based mechanism.
The documentation, comments, and format of the post-install scripts
have been extended and reworked.

(cherry picked from commit 9f28557a)

A custom devicetree can be set via the -d parameter on the fng-install
script. Since the re-work of the post-install scripts, the parameter
wasn't applied correctly (when no overlays were set).
Fixed the setting of the devicetree parameter in the boot.cfg, to
re-enable to correct loading of custom devicetrees.

Use the latest seco-show-demo:
* Rename the guf-show-demo to seco-show-demo
* Pull from ew2022 branch
* Also some slides needed refinement.

The Kirkstone-based Flash-N-Go System (plus the kernel) is slightly bigger
than the current 64MB partition size. Increased the size to 128 MB for now.
In the future, compressing the kernel would be a better solution.

Info: Self-extracting kernels are not yet supported on ARM64. We, therefore,
use an uncompressed kernel at the moment.

The selection of the partition scheme was still dependent on the old
machine names and was therefore broken (the selection was falling back
to the i.MX6 scheme).

The generic artefact names (like Image), had to be removed with
Kirkstone. The artefacts now have extended names, that must be
used during the generation of the batch/shell scripts for calling
UUU.

For more info see commit 0272dbc3.

Removed guf-show-demo2 package since we do not use it anymore. If we need
an additional demo instance again, we should use an additional systemd unit
file instead of adding a complete package.

BCS 746-000810

(cherry picked from commit 4606414f)

It is best practice to don't run services as root. The qt-compositor
service now runs under the qt username.
The commit also contains a draft of the systemd socket-based activation
mechanism. Unfortunately, the qt-compositor daemon doesn't handle the transfer
of the socket from the socket unit to the service unit properly.
Until the daemon is fixed, the service still needs to be started manually.

Moved the profiles with the environment initialization into a new
sub-folder and activated them by linking to the sub-directory.
The reason for this is, that weston and the qt-compositor need
different environments and we want an easy way of exchanging them.
The wayland related parts have been moved from the qtenv to weston
and qt-compositor.

The hardware-cursor is rendered outside of Qt and doesn't properly
display when the screen is rotated via the qt-compositor.
The qt-compositor can display the cursor itself, which might be the
preferred way.

Changed the qt-multi-screen-compositor to run under the qt username.
Fixed the file names of the systemd service units and
added the creation of the qt user to the recipe.

The qt-multi-screen-compositor will run under the "qt" username
in the future. Renamed the systemd service files to reflect the
change.

Also cleanup the output a little.
Make sure that the prepare_rtc script only affects Tanaro devices

The overlays no live directly in /boot without a subfolder

For GPL-3.0 free images dosfstools are not available.