--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@543a2170

manifest_package: add release suffix

Customer specific manifest projects can now set the RELEASE_SUFFIX
variable, which then gets appended to the deployment folder names.

--

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

alphaplan_fwr: change variable "release_name_local" to "release_name"

Otherwise it can be assumed that it might be correlated with
outputdir_local, which is not the case.

--

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

package_release: more refactoring

- Make output-dir an argument that can be passed multiple times instead
  of hard-coding two dirs with certain meanings.
- Remove LOCALDIR variable from package.env, because it is not used
  anywhere (only occurence was job class ".uploadsdkftp" which wasn't
  used anywhere either).

--

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

package_release: refactoring

Improve readability of package_release.py and its submodule
generate_release_metadata.py.

- Add describing comments throughout the file.
- Remove duplicate code from functions. Simplify them, so that they do
  what their names say (and nothing more).
- Rename variables and function arguments to make their purpose clearer.
- Harmonize variable names with their corresponding command line arguments.
- Add pydoc for functions.
- Add type declarations to function arguments.
- Generate MD5 and metadata files in the source directories so that they
  can be copied along with the rest of the files.

Per customer request add QStylesheetStyle patch form Qt 5.15.4.
See also https://bugreports.qt.io/browse/QTBUG-89366
         https://bugreports.qt.io/browse/QTBUG-86857
         https://codereview.qt-project.org/c/qt/qtbase/+/327897

This patch can be omitted when a later Qt Commercial version is used.

Felix Gerking authored 2 years ago and Tobias Kahlki committed 2 years ago

phytool is used for ethernet compliance tests.

The DISPLAY environment variable must be set for X applications to start
correctly.

The Weston systemd service was depending on the graphical.target. This target
depends on a display manager which we don't have. Replaced it with the
multi-user.target.

The seco-pnmtologo tool is a variant of the in-kernel pnmtologo tool.
See also https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/video/logo/pnmtologo.c?h=v5.15.71

The SECO Northern Europe variant adds a binary output mode. The binary
output can be used by the SECO Northern Europe boot logo implementation.

Use oelint-adv to lint the recipe.

To reduce the number of files of the logo package.
Introduce a library package as well.

This is mainly major recipe refactoring. Using the oelint-adv tool add
more information to the recipe.

Also fix a QA issue of .so libs being actual files instead of links

The netpbm package uses the LDSHLIB variable to build the shared
libraries. Inside Yocto the libs need to be built with GNU_HASH and
assume that LDFLASG are being used.

Thus add LDFLAGS to the LDSHLIB variable in the netpbm config file.

The standalone package of xwayland is preffered over the package from
xserver-xorg.

See https://git.yoctoproject.org/poky/commit/meta/recipes-graphics/
xwayland?h=kirkstone&id=07d33c8ec848c257c014fbef1241104847873d5f and
https://fedoraproject.org/wiki/Changes/XwaylandStandalone

Tobias Kahlki authored 2 years ago and Tobias Kahlki committed 2 years ago

The removal of networkd is done via "remove-variable" which isn't explained
sufficiently. Added a comment regarding the concrete operation of the
"remove-variable".

Tobias Kahlki authored 2 years ago and Tobias Kahlki committed 2 years ago

The getty service starts a default instance on tty1. This instance appears as
a login prompt on our HMIs which isn't the expected behavior for our customers.
The patch removes the installation of the default instance.

Clemens Terasa authored 2 years ago and Tobias Kahlki committed 2 years ago

The Yocto system for appending and removing items form lists executes
the removal as a last step. After a removal an item cannot be
appended.

For the DISTRO_FEATURES this means that the once removed "x11" item
cannot be appended in later steps or dependent layers.

This can be circumvented by the introduction of intermediate variables
or by using such variables.

For example poky defines DISTRO_FEATURES as follows
```
DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${POKY_DEFAULT_DISTRO_FEATURES}"
```
To remove an item from the DISTRO_FEATURES you can instead remove it
form one of the variables i.e. the DISTRO_FEATURES_DEFAULT variable.

Thus remove the `bluetooth` and `x11` items from the
DISTRO_FEATURES_DEFAULT to be able to re-add them to DISTRO_FEATURES
later.

--

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

get_integration_sources: check if CI is enabled

Trying to query CI variables on a project which does not have the CI
feature enabled leads to an HTTP 403 (forbidden) error.
Check whether CI is enabled using the "jobs_enabled" flag.

Tobias Kahlki authored 2 years ago and Tobias Kahlki committed 2 years ago

The "target" parameter was colliding with the TFTP parameter. Removed the
shortcut (-t) for the target parameter to resolve the collision.
Also, some filesystem operations weren't respecting the TARGETDEVICE
parameter.

The patches 0001-Add-clear-bg-show-logo-and-show-progress-bar-switche.patch and
0002-Adjust-the-colors-for-the-G-F-logo.patch were out of sync with
upstream. Sync them with
```
devtool modify psplash
devtool update-recipe psplash -a ../sources/meta-seconorth-distro --force-patch-refresh
devtool reset psplash
```

BCS 746-001043

BCS 746-001043

--

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

CI:deploy: fix fngsystem deployment path

The match to detect fngsystem still contained 'guf'. Changed to 'seco'.

BCS 746-001043

The appendfile didn't worked correctly because of the renamed directory
and thus the blacklisting didn't worked anymore. This fixes it.
Also added a rule to ignore only the internal emmc, so removing of the
'disable_all' file, does not mount the internal partitions
automatically.

--

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

Make check error message more verbose

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@21e7edeb

Improve ci-test build

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@76bd81d8

Fix check job rules

--

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

Move check job to parent pipeline

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@593784e1

Refactor check_if_integration_branch_is_up_to_date

- Use "source" and "target" terminology in the script, just like in the
  GitLab CI variables.
- Spefify data types for function arguments.
- Rename function arguments to better reflect their data types.
- Move determination of integration branch into main function, so that
  the successfull status message can be more verbose.
- Remove parent_merge_request feature and checking for gitlab-ci
  integrations, because the check job does not run on gitlab-ci
  integration branches at all.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@45b49ee3

Remove build stage on master

We don't need to explicitly trigger a build after merging changes in
gitlab-ci. A master pipeline on the target projects runs automatically.

BCS 746-001018

The gpiod tools are required for the production tests on the i.MX8
devices.

BCS 746-001028

The image has increased in size and doesn't fit anymore.
This also correlates to the increased size of the recovery partition
size (see f0471f13).


(cherry picked from commit 57bc20c1)

Added optional --left and --right flags to the dualscreen scripts. These
flags allow to test the left or right screen individually.

BCS 746-000870

Gitlab uses textfiles to present links when downloaded.
Handle these during file download.

beep should be used to test onboard buzzers.

--

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

Rename pipeline stages to reflect YAML filenames

--

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

Really fix potential error message in retrigger job

TypeError: 'NoneType' object is not subscriptable

Example:
https://git.seco.com/seco-ne/yocto/manifest/-/jobs/129201

--

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.